Thank you, I tried doing it the first way. I configured the kernel to include DDB, then typed on the console:
sysctl debug.kdb.enter=1 to enter DDB. Then typed this to force a panic: sysctl debug.kdb.panic=1 The computer just hung after this, and after waiting for a while I pressed the reboot button. It said "no core dumps found" while rebooting. I couldn't find any core dumps in /var/crash either. So I tried again to enter DDB, typed sysctl debug.kdb.enter=1. Now the computer hangs even for this (tried it twice)! What did I do wrong? Please help me with the steps. On 14 March 2012 22:49, Artem Belevich <[email protected]> wrote: > On Wed, Mar 14, 2012 at 9:31 AM, Maninya M <[email protected]> wrote: > > How can I capture the states of all running processes at a particular > point > > in time? How can I retrieve this information for later use? > > Go into DDB. Do 'panic'. wait for the kernel to finish dumping core. > Once system reboots and saves kernel core, examine process state in > the core file with gdb. Obviously it's a postmortem examination which > may not be exactly what you want. > > Less destructive option would be to do 'ps' or 'show threads' in DDB, > save its output and then continue. > > --Artem > -- Maninya -- Maninya _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[email protected]"
