Messages in this thread | | | Date | Mon, 28 Apr 2008 08:34:45 -0500 | From | Jason Wessel <> | Subject | Re: kgdb over ethernet? |
| |
Jan Engelhardt wrote: > On Friday 2008-04-25 19:32, Jason Wessel wrote: >> Jan Engelhardt wrote: >>> the DocBook files for the recently-merged kgdb mention kgdboe, as does >>> the doc on kgdb.sf.net, but I do not see kgdboe anywhere in the source. >>> Is oe actually merged? I'm kinda short on rs232... >> Well if you have at least one you have enough because you can share kgdb >> with the console. > > kgdb is running, though I wonder why breakpoints are not seemingly hit. > > (gdb) b vfs_readdir > cBreakpoint 2 at 0xc0270c11: file fs/readdir.c, line 23. > (gdb) c > Continuing. > > Then I issued ls -l on tty1 (kgdb is on ttyS0), but it did not > happen to stop at vfs_readdir, though I would assume vfs_readdir > was entered as part of /bin/ls. > Ideas?
I know very little about what vmware may or may not be doing here.
I tried your test with the tip of the kernel tree this morning with a arch=i386 kernel and it seems to work fine on real HW and qemu. You might consider checking if the kgdb regression tests pass. You can change your .config to have:
CONFIG_KGDB_TESTS=y CONFIG_KGDB_TESTS_ON_BOOT=y CONFIG_KGDB_TESTS_BOOT_STRING="V1F100"
This will verify if the kgdb core is work correctly on your platform, and if some part fails we can go from there. Depending on if vmware implements HW breakpoints the HW breakpoint tests could certainly fail. As an example, qemu does not implement HW breakpoints so those particular tests always fail, but the failure does not kill the kernel and the test suite simply moves on to the next test.
Jason.
| |