Re: too many warning messages from gnumach

[Samuel Thibault]

Samuel Thibault, le Tue 16 Mar 2010 13:59:11 +0100, a écrit :
> Get the address of the mach_port_deallocate_debug variable, set it to 1
> by entering kdb and use
> 
> w theaddress 1
> 
> then trigger the warning, you'll now get kdb invoked from the context.
> Then you can use trace to get the backtrace, and "show all thread/u" to
> know which process the task corresponds to. Then you can use e.g. gdb to
> know exactly which mach_port_deallocate() call is apparently spurious.

I forgot: of course you can then set back mach_port_deallocate_debug to
0 and use continue to let the system continue working as usual.

Samuel