This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

backtrace in core mode(linux kernel /proc/kcore)


Hi,

I can display kernel data structures by debugging in core mode
with the /proc/kcore file and giving the elf image of the kernel 
built with symbols(gdb vmlinux /proc/kcore). But, i am unable to
do a backtrace of a task's kernel stack. I know the stack pointer
of a task, but i am unable to set it via >frame address < cmd.

Inside the backtrace_command_1 function, the current frame is
got, if i build a frame with hardcoded fp,pc values, it works - i
get a proper stack backtrace. But there must be standard way to
get this done. This is needed even for userland debugging, when
we have multiple threads and so multiple stacks, and i am doing
the context switching myself(not a standard thread library).

thanks in advance
sangam
______________________________________________
@Mail.ru  Национальная почтовая служба
http://www.mail.ru
______________________________________________
На правах рекламы:
Закажи футболку с собственным e-mail адресом!
http://r.mail.ru/cln1956/souvenir.mail.ru


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]