On Fri, 23 Jun 2000, Raj, Ashok wrote:
> 1. Iam only getting addrses printed for stack trace instead of symbols, how
> would i be able to get symbol table info
> to the debugger.
>
> for user programs we do gdb <file> <core>
gdb vmlinux
make sure that the vmlinux you are using is the one the system is using.
> 2. If i started without the gdb option, can i still be able to reconnect to
> the debugger?
My patch on the downloads (the rh62 one) page allows you to connect to the
debugger with SysRq-g. (Thats shift-alt-print-scrn-q I think. SysRq
support has to be enabled in the kernel and not deactivated by boot
scripts)
> 3. if i get disconnected from gdb for some reason, and i started with the
> gdb option in lilo, can i reconnect back the kernel?
See above. Also, any time the system hits a breakpoint, it will block for
the debugger. The debugger session does not need to be the same...
> 4. if i have modules how i would be able to debug that.
Carefully.
See the kgdb project on sourceforge for more help. I manage without
accessing global variables and recognizing/handling the obviously wrong
output. YMMV.
The key command is "add-symbol-file <path to module> 0x<address of .text
section>
Remember to load the module with the '-m' option to insmod to get the
section information.
--
dougk@xxxxxxxxxxx
dkilpatr@xxxxxxx
|