Is ctl-alt-esc "working" for others on 8.x & 9.x?
See
http://forums.freebsd.org/showthread.php?t=40111
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-qu
owing lines:
console="comconsole vidconsole"
comconsole_speed=9600
hint.uart.0.flags="0x90"
I invoke the kernel debugger on the target using:
'sysctl debug.kdb.enter=1'
Which gets me to the DB> prompt where I enter the following:
DB>gdb
Step to enter the gdb debug
ezes on average once a week but doesn't panic, so i would like to
> enter the kernel debugger, to at least being able to force a panic.
> Unfortunately, i have no serial interface and can't enter into the
> debugger on the console using ctrl-alt-esc either, because it conflicts
&g
Hi all
I have an unstable machine running FreeBSD 8.0-RELEASE inside vmware. It
freezes on average once a week but doesn't panic, so i would like to
enter the kernel debugger, to at least being able to force a panic.
Unfortunately, i have no serial interface and can't enter into the
d
I've been having problem with the kernel debugger on one of my
machines, and the time has come to try and hunt the critter down.
The machine in question is running -CURRENT; I'm not posting to that
list because I first noticed the problem when it was running -Stable
some
Hi!
We have some networking problem, with PF and route-to, actually,
system locks and
sends junk to net. But I'm able to enter debugger. Is it possible to
localize problem using it?
I have acess to console and get do debugger prompt. I'd like to make
proper report using debugger to send to freebsd-
On Tuesday, 24 February 2004 at 11:23:40 +0530, [EMAIL PROTECTED] wrote:
>
> I need to use a kernel debugger on FreeBSD 4.8 to check if
> my messages to the kernel have all the info required and if
> Is being processed.
I don't really understand what you mean here.
>
I need to use a kernel debugger on FreeBSD 4.8 to check if
my messages to the kernel have all the info required and if
Is being processed.
DDB is the debugger mentioned in the handbook. Will DDB help
Me debug the kernel on the target itself? All that I have read
abt DDB is debugging from a
> how can i break into the kernel debugger when the console
>>> is a serial one? (Ctrl-Alt-Esc has now ascii equivalent :-)
>>
>> Try:
>>
>> sysctl debug.enter_debugger=gdb
>>
>> to go into gdb, or
>>
>> sysctl debug.enter_debugger=dd
