Re: gdb does not analyse vmcore from kexec on 2.6.20

[Rajesham Gajjela <rajeshamg@xxxxxxxxx>]

> I was running linux-2.6.20 on x86_64 & my machine's
> RAM is > 4GB.
> 
> Got the vmcore file (after following the steps in
> Documentation/kdump/kdump.txt).
> 
> To analyse the core file, I am using gdb
> (version-6.4). Issues that I am facing with this:
>  1)"bt" gives me the stack from cpu-0 (ideally I
> think, it should give the thread that
>     was running when panic happened)
>  2) "info threads" is giving me only the threads on
> all the cpus 

Just to clarify, "info threads" is giving only
the "current" thread on each CPU.


> (e.g, I have 2 CPUs on my
>     system, so, I was getting only two threads). Its
> not giving the rest of the threads that are
>     active (may be sleeping or doing some thing
> else). In general, I dont get, the threads from
>     per cpu runque.
> 
> In general, do you guys claim that gdb analyses the
> cores from kexec is reliable.

What do you guys recomment to analyse the cores ?
gdb or crash ?
gdb seems to have the issues pointed above. Is there
any body successfully used gdb ?


> 
> How ever, I can see that Dave's crash tool works
> fine against to the same vmcore.



 
____________________________________________________________________________________
Sucker-punch spam with award-winning protection. 
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html
_______________________________________________
fastboot mailing list
fastboot@xxxxxxxxxxxxxx
https://lists.osdl.org/mailman/listinfo/fastboot