debugging core dumps on other computer

[Bruno Gonzalez (STenyaK)]

(first of all, sorry if this is not the correct place to ask, but i
couldn't find a better one...)

I'm new to debugging using core dumps. I've managed to get core dumps
+ symbols using g++ and gdb under linux.
I compile using g++ -g -dH, and i debug using gdb executableFile -c
coredumpFile.


This is a test program backtrace in the original computer (a gentoo
box), where the program was compiled, run, and coredumped:
(gdb) bt
#0 0xffffe410 in __kernel_vsysca ll ()
#1 0x4017a101 in raise () from /lib/libc.so.6
#2 0x4017b8e8 in abort () from /lib/libc.so.6
#3 0x400ed794 in __gnu_cxx::__ve rbose_terminate _handler () from /usr/
lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6
#4 0x400eb1b5 in ?? () from /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/
libstdc++.so.6
#5 0x400eb1f2 in std::terminate () from /usr/lib/gcc/i686-pc-linux-
gnu/4.1.2/libstdc++.so.6
#6 0x400eb2aa in __cxa_rethrow () from /usr/lib/gcc/i686-pc-linux-gnu/
4.1.2/libstdc++.so.6
#7 0x08049047 in main () at main.cpp:46

And this is what i get after i scp the exe and dump to a different
computer (a kubuntu box):
(gdb) bt
#0 0xffffe410 in __kernel_vsysca ll ()
#1 0x4017a101 in modff () from /lib/libc.so.6
#2 0x4017b8e8 in sigorset () from /lib/libc.so.6
#3 0x400ed794 in ?? ()
#4 0x0804c038 in ?? ()
#5 0x00000001 in ?? ()
#6 0x00000002 in ?? ()
#7 0x4027d560 in ?? () from /lib/libc.so.6
#8 0x40035000 in ?? ()
#9 0x00000001 in ?? ()
#10 0x0804c060 in ?? ()
#11 0x4000d6e9 in ?? () from /lib/ld-linux.so.2
#12 0x400351b8 in ?? ()
#13 0x40035c10 in ?? ()
#14 0x00000000 in ?? ()

As you can see, the backtraces differ, and i lose almost all symbols.
What am i doing wrong? Thanks in advance!

[Ian Collins]

Re: debugging core dumps on other computer

Bruno Gonzalez (STenyaK) wrote:

(first of all, sorry if this is not the correct place to ask, but i
couldn't find a better one...)
>

I'm afraid it isn't the correct place, one of the Linux or GNU groups
would be better.

--
Ian Collins.

[red floyd]

Re: debugging core dumps on other computer

Bruno Gonzalez (STenyaK) wrote:

(first of all, sorry if this is not the correct place to ask, but i
couldn't find a better one...)
>
I'm new to debugging using core dumps. I've managed to get core dumps
+ symbols using g++ and gdb under linux.
I compile using g++ -g -dH, and i debug using gdb executableFile -c
coredumpFile.
>
>
This is a test program backtrace in the original computer (a gentoo
box), where the program was compiled, run, and coredumped:
(gdb) bt
#0 0xffffe410 in __kernel_vsysca ll ()
#1 0x4017a101 in raise () from /lib/libc.so.6
#2 0x4017b8e8 in abort () from /lib/libc.so.6
#3 0x400ed794 in __gnu_cxx::__ve rbose_terminate _handler () from /usr/
lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6
#4 0x400eb1b5 in ?? () from /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/
libstdc++.so.6
#5 0x400eb1f2 in std::terminate () from /usr/lib/gcc/i686-pc-linux-
gnu/4.1.2/libstdc++.so.6
#6 0x400eb2aa in __cxa_rethrow () from /usr/lib/gcc/i686-pc-linux-gnu/
4.1.2/libstdc++.so.6
#7 0x08049047 in main () at main.cpp:46
>
And this is what i get after i scp the exe and dump to a different
computer (a kubuntu box):
(gdb) bt
#0 0xffffe410 in __kernel_vsysca ll ()
#1 0x4017a101 in modff () from /lib/libc.so.6
#2 0x4017b8e8 in sigorset () from /lib/libc.so.6
#3 0x400ed794 in ?? ()
#4 0x0804c038 in ?? ()
#5 0x00000001 in ?? ()
#6 0x00000002 in ?? ()
#7 0x4027d560 in ?? () from /lib/libc.so.6
#8 0x40035000 in ?? ()
#9 0x00000001 in ?? ()
#10 0x0804c060 in ?? ()
#11 0x4000d6e9 in ?? () from /lib/ld-linux.so.2
#12 0x400351b8 in ?? ()
#13 0x40035c10 in ?? ()
#14 0x00000000 in ?? ()
>
As you can see, the backtraces differ, and i lose almost all symbols.
What am i doing wrong? Thanks in advance!

Wrong group. Try gnu.g++.help

F/U set.