[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: too many warning messages from gnumach

From: Samuel Thibault
Subject: Re: too many warning messages from gnumach
Date: Tue, 16 Mar 2010 14:11:18 +0100
User-agent: Mutt/1.5.12-2006-07-14

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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]