On 3/14/12 12:02 PM, Artem Belevich wrote:
On Wed, Mar 14, 2012 at 11:25 AM, Maninya M 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.
On Wed, Mar 14, 2012 at 11:25 AM, Maninya M 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 s
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
On Tue, Mar 13, 2012 at 10:34 PM, Fernando Apesteguía
wrote:
> On Tue, Mar 13, 2012 at 12:23 AM, Ryan Stone wrote:
>> 2012/3/12 Fernando Apesteguía :
>>> I'm using 9.0-RELEASE.
>>>
>>> I downloaded the snapshot "9.0-CURRENT-201012" and tried to build it's
>>> kernel but I get this error:
>>>
>>>
On Wed, Mar 14, 2012 at 9:31 AM, Maninya M 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 c
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?
--
Maninya
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To
On 3/13/12 10:47 PM, Devin Teske wrote:
On Mar 6, 2012, at 1:10 AM, Alexander Best wrote:
great work. a few questions or rather suggestions:
[snip]
2) the highlighted first letters suggest that these are shortcuts. they work
great for the actual menu items, but for "" and"",
pressing
7 matches
Mail list logo