Frank Schaefer wrote: > Finally I found some time to complete the kgdb setup, but another > problem arises. > I've set up the hardware, and develhost and testhost communicate via > ttyS0. > The debugger (gdb-5.0) starts up with ``gdb vmlinux''. The plain 2.4.16 > kernel on the testhost runs fine. If I choose Linux-2.4.16-kgdb from the > lilo prompt, the testhost simply reboots bringing me back to the lilo > prompt. > > I've followed the doc from kgdb.sourgeforge.net exactly. At least I > think so -- did it three times getting the same results. > > The develhost is a i686-pc-linux-gnu (linux-2.4.16, glibc-2.2.4, > gcc-2.95.3+glibc-2-patch) LFS system. > The testhost is a fairly old Slackware 7.0.0 system. Here I've upgraded > the modutils to 2.4.6, and the kernel ( of course ). > > Furtheron has the develhost his root on /dev/hda1 whereas the testhost > has it on /dev/hdb1. Running ``rdev bzImage-kgdb /dev/hdb1'' didn't > change anything ( shouldn't using lilo ). > Here is the lilo.conf section for the kgdb kernel: > > image=bzImage-kgdb > root=/dev/hdb1 > labe=Linux-kgdb > read-only > append="gdb gdbttyS=0 gdbbaud=115200" > > Any idea? - Are you using the same .config file? Try to load the 2.4.16 config file and add the debugging options. - Try to comment the append line "gdb ..." in the lilo.conf file and test if the machine boots.( You can activate the debugger with the startkgdb program later). Regards, Juan Antonio -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
