Re: Lion panic debugging
Re: Lion panic debugging
- Subject: Re: Lion panic debugging
- From: Kevin Brock <email@hidden>
- Date: Wed, 27 Jul 2011 14:00:54 -0700
On Jul 27, 2011, at 12:55 PM, Brian Bechtel wrote:
I believe you aren't specifying "-arch i386" on your gdb command line.
Ahh… it was something simple. You're right, I wasn't. It'd been a while since I looked at a backtrace on an x86_64 system.
have a list of zones with more than 1 million allocations, and a
backtrace of the suggested leaking code (a new feature in Lion.) That
backtrace should be examined, rather than the backtrace of the panic.
In this case that list of suspected modules is:
Backtrace suspected of leaking: (outstanding bytes: 172088) 0x245069 0x27e164 0x23837c 0x5645bf 0x5646e9 0x564b06 0x564c4d 0x5f015a
Which is just part of the backtrace:
0x245069 <zalloc+25>: add $0x8,%esp
0x27e164 <_vm_map_entry_create+30>: mov êx,ëx
0x23837c <task_create_internal+60>: jmp 0x2383c9 <task_create_internal+137>
0x5645bf <fork_create_child+47>: test êx,êx
0x5646e9 <cloneproc+73>: test êx,êx
0x564b06 <fork1+662>: test êx,êx
0x564c4d <fork+45>: test êx,êx
0x5f015a <unix_syscall64+554>: cmpl $0x0,0x114(%esi)
If the list really is where the leak is occurring, it would seem to be related to many forks…
Thanks.
Kevin
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden