I'm having problems getting kgdb working and was hoping someone could point
out what I'm doing wrong. Remote gdb is really my last hope. I tried getting
crash dumps working, and that failed. I tried the kernel debugger and that
failed. I'm hoping I can get this up in the air so I can work on some issues
this week. :-)
I've got the patch for RH 6.2 kernel and it applied clean. No problems
there.
Built the kernel and selected the CONFIG_GDB option.
make dep, make bzImage, make modules, blah blah. All worked fine.
I put an entry in my lilo.conf file that reads:
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux-gdb
image=/boot/vmlinuz-2.2.14-gdb
append="gdb gdbttyS=0 gdbbaud=9600"
label=linux-gdb
initrd=/boot/initrd-2.2.14-5.0smp.img
read-only
root=/dev/sda1
I then reran lilo (with no complaints) and rebooted my machine.
On my (dare I say it) NT box. I'm running CRT with a serial cable hooked
from com2 on my NT box to com1 on my linux box. The settings for my term
are:
port: com2
baud: 9600
data: 8
part: none
stop: 1
no flow control.
When I reboot the linux-gdb kernel it never stops. It just happily boots up
and never asks for input from the serial port.
I've tried removing the append string and specifying it on the command line
with no luck.
Any Ideas what I'm doing wrong?
I've signed up for the list, but haven't had a response back, so if you
reply please copy me. Thanks.
-bmb-
Brian M. Boerner
System Software Developer
Adaptec, Inc.
Nashua, NH 03060
(603) 579-4625
|