Problems with gdb on 64 bit systems

Problems with gdb on 64 bit systems

[sudhakar govindavajhala]

Hi all

On a 64 bit system, I am unable to read any core dump in gdb.    I
generated the core dumps in two ways: via null pointer derefernce in
program and via gdb attach and gcore.

In both the cases, I am unable to read the core files. Do you have any thoughts?

I tried with both gdb 7 and gdb 6.7.

For gdb 7, I tried two different  machines maintained by different
organizations to see what the issue may be.  Both are failing.

Thanks,
--sudhakar

Re: Problems with gdb on 64 bit systems

[Jan Kratochvil]

On Sat, 28 Jan 2012 00:33:01 +0100, sudhakar govindavajhala wrote:
> On a 64 bit system, I am unable to read any core dump in gdb.    I
> generated the core dumps in two ways: via null pointer derefernce in
> program and via gdb attach and gcore.
> 
> In both the cases, I am unable to read the core files. Do you have any thoughts?

Works for me on Fedora 16 x86_64:

$ echo 'f(){*(int*)0=0;}main(){f();}'|cc -x c -;(ulimit -c unlimited;./a.out);gdb -batch ./a.out ./core.* -ex bt 
[New LWP 11907]
Missing separate debuginfo for 
Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/1e/2a683b7d877576970e4275d41a6aaec280795e
Core was generated by `./a.out'.
Program terminated with signal 11, Segmentation fault.
#0  0x000000000040047d in f ()
#0  0x000000000040047d in f ()
#1  0x0000000000400493 in main ()


> For gdb 7, I tried two different  machines maintained by different
> organizations to see what the issue may be.  Both are failing.

You need to be more specific.  And best to submit the problem for GDB release
by that OS vendor.


Regards,
Jan