Date: Fri, 16 Mar 2012 11:19:05 +0530 From: Maninya M <maninya@gmail.com> To: Julian Elischer <julian@freebsd.org>, Artem Belevich <art@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Capture states of all processes at the same time Message-ID: <CAC46K3kOh0yPn6KQDK0ZYWMHGjUjaV75ZDw3YMOPFtcKg76s_w@mail.gmail.com> In-Reply-To: <4F60FF28.8010104@freebsd.org> References: <CAC46K3mNJQDf%2BKqA0YYiAXXdyjhU3iSX8V-5%2B2rF8Ah0aH-7rA@mail.gmail.com> <CAFqOu6i1TY-4FcGYEqvD00uz2qx9yL971s0Ca6PsxEVSTjnCSQ@mail.gmail.com> <CAC46K3kcuoDt92tj5yQN2E9Aj%2BRVihaA-NXUTaZBm8WFGZVC-Q@mail.gmail.com> <CAC46K3=Kq=J9fqfyV8FewmE49gcNh_C-rmL4rZu1PrRicTvhGA@mail.gmail.com> <CAFqOu6gkzk4A_o74P4fd-q8RDHsHy88grEg1G7ksc2tjwV6UFA@mail.gmail.com> <4F60FF28.8010104@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I am unable to enter DDB. I used the command from this link: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html where it says: ------ The second scenario is to drop to the debugger once the system has booted. There are two simple ways to accomplish this. If you would like to break to the debugger from the command prompt, simply type the command: # sysctl debug.kdb.enter=1 ------ But when I type that the computer hangs! What do I do? My primary aim is to get the process states of all processes running at a particular time, save them and be able to retrieve them when needed so I can run the processes from those states. Also how can I know in which CPU (I am using an intel i5 multicore system) core each process is running? On 15 March 2012 01:57, Julian Elischer <julian@freebsd.org> wrote: > On 3/14/12 12:02 PM, Artem Belevich wrote: > >> On Wed, Mar 14, 2012 at 11:25 AM, Maninya M<maninya@gmail.com> wrote: >> >>> 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. >>> >> First, make sure you have swap space configured. If minidump is not >> enabled (check sysctl debug.minidump) you will need to make sure you >> have more swap space than physical memory. >> Then make sure that dump device is set up correctly. See dumpdev in >> rc.conf(5) >> >> If that didn't work, you may be running into the issue in PR kern/155421: >> http://www.freebsd.org/cgi/**query-pr.cgi?pr=kern%2F155421&**cat=<http://www.freebsd.org/cgi/query-pr.cgi?pr=kern%2F155421&cat=>; >> >> Alas, I don't know what to do about that. >> > > or just do "ps" from ddb and then continue. > > you can set things up in 9 (and maybe 8, I don't know) to capture the ddb > output.. > > > --Artem >> ______________________________**_________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/**mailman/listinfo/freebsd-**hackers<http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>; >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@** >> freebsd.org <freebsd-hackers-unsubscribe@freebsd.org>" >> >> > -- Maninya
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAC46K3kOh0yPn6KQDK0ZYWMHGjUjaV75ZDw3YMOPFtcKg76s_w>