From: Greg B. <gb...@po...> - 2000-09-01 05:43:48
|
Stuart Menefy wrote: > > Folks > > I've added a few pages to the web site describing how to use GDB to boot > and debug a target system. > > They should appear at: > http://linuxsh.sourceforge.net/docs/gdb.php3 > > (Greg, is there any way to kick the web site building process?) Sort of. You can run the ~gnb/bin/update-web shell script, but because of the cheap&nasty way I wrote it there some problems with permissions if anyone other than me does it. Fixing this is somewhere on the TODO list... > > Any comments welcome. > Your documentation is very good...easy to read, accurate and up-to-date. Well, mostly, I've got a few comments (see below). Actually I was wondering if I could basically subsume large chunks of it into the FAQ (with full credit of course!) ? The idea is that someone could print out the FAQ and have almost all the info they need in one document. Given the current state of the FAQ it needs a major clue-transfusion. Anyway, my comments on gdb.php: 1. "Note 'GDB Stub kernel debug' and 'Early printk support' are mutually exclusive." AFAICT this is not true, at least it's not supposed to be. If something in the code or doco suggests that, I need to fix it! 2. In the 3rd-last paragraph, it talks about the stub detaching from the host gdb. Perhaps it might be a good idea to mention the message gdb gives, which is probably quite confusing for newbies. BTW when building a debugging kernel, has anyone tried removing the -fomit-frame-pointer flag from the compile? I believe this will enable gdb to show a kernel stack trace. The ARM port has a config variable, CONFIG_FRAME_POINTER, to do this. Greg. -- These are my opinions not PPIs. |