On Tue, Apr 5, 2011 at 1:33 PM, Julian Elischer <julian_at_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 what >>> we would need to put on the stack at fork_exit() to make it stop when it >>> gets there? >>> >>> not only is it annoying but it slows down debugging because kgdb and the >>> 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 end >>> of a stack. >>> >>> Julian >> >> From my experience, it checks for a NULL stack chain pointer. Once that >> 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. NavdeepReceived on Tue Apr 05 2011 - 19:02:49 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:13 UTC