Date: Tue, 5 Apr 2011 13:35:44 -0700 From: Navdeep Parhar <nparhar@gmail.com> To: Julian Elischer <julian@freebsd.org> Cc: Justin Hibbits <chmeeedalf@gmail.com>, FreeBSD Current <current@freebsd.org> Subject: Re: KGDB stack traces in the kernel. Message-ID: <BANLkTinPdVUac6YGwf4GvOE7gtndbQERaQ@mail.gmail.com> In-Reply-To: <4D9B7C92.6030901@freebsd.org> References: <4D9A4CE5.5090900@freebsd.org> <ACA0C058-28F4-4A0E-B9EC-E26E35219449@gmail.com> <4D9B7C92.6030901@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 5, 2011 at 1:33 PM, Julian Elischer <julian@freebsd.org> wrote: > On 4/4/11 6:04 PM, Justin Hibbits wrote: >> >> On Apr 4, 2011, at 6:57 PM, Julian Elischer wrote: >>> >>> is there anyone here with enough gdb/kgdb source experience to know wha= t >>> we would need to put on the stack at fork_exit() to make it stop when i= t >>> gets there? >>> >>> not only is it annoying but it slows down debugging because kgdb and th= e >>> ddd >>> front end ask for stacks a LOT. sometimes it actually just hangs as the >>> stack >>> goes into a loop and never ends. >>> >>> I had a quick look but didn't spot how gdb decides it has reached the e= nd >>> of a stack. >>> >>> Julian >> >> From my experience, it checks for a NULL stack chain pointer. =A0Once th= at >> reaches NULL, it's the end of the stack. >> >> - Justin >> > I'll try adding NULL when we build the intial stack up. > :-) What does ddb do? It always seems to get this stuff correct. Navdeep
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTinPdVUac6YGwf4GvOE7gtndbQERaQ>