Re: Unbalbe to gdb core file generted from customer machine on local host

[James C Chen]

Thank you very much Sergio.

You have answered my question. I was suspecting that the difference in
version of library is the cause.

Best Regards,

James Chen
IBM


From:   Sergio Durigan Junior <address@hidden>
To:     James C Chen/Ontario/address@hidden
Cc:     address@hidden
Date:   11/17/2014 03:28 PM
Subject:        Re: Unbalbe to gdb core file generted from customer machine on
            local host



On Sunday, November 16 2014, James C. Chen wrote:

> Hi there,
>
> Thanks for providing gdb support.

Hello, James.

First of all, this mailing list is not used by the GDB project anymore.
You should write to <address@hidden>, which is the official mailing
list for the project.

> I created an executable binary (x86-64) on my local Linux server and let
it
> run on customer Linux server. Later on, my binary generated a core
> file.  I tried to gdb the core file on my local Linux server, but I can
not
> get correct stack trace.

It is not clear whether you compiled your binary with debug information
or not.  Have you used the -g flag on GCC?  Also, if your binary is
linked against shared libraries, you have to make sure that the debug
information for those libraries is also installed.  And you have to make
sure that the versions of the libraries installed on your machine and on
your client's machine are the same.

> (gdb) bt full
> #0  0x0000003a5d07288e in ?? ()
> No symbol table info available.
> #1  0x000000001b36d548 in ?? ()
> No symbol table info available.
> #2  0x000000001b2fab70 in ?? ()
> No symbol table info available.
> #3  0x00007fff60c30a9c in ?? ()
> No symbol table info available.
> #4  0x000000001b36d548 in ?? ()
> No symbol table info available.
> #5  0x000000001aafc860 in ?? ()
> No symbol table info available.
> #6  0x0000000000002230 in ?? () from /lib64/libm.so.6
> No symbol table info available.
> #7  0x545194cc00000221 in ?? ()
> No symbol table info available.
> #8  0x0000000000000000 in ?? ()
> No symbol table info available.

These errors happen when GDB does not have access to the debug
information of your binary/libraries.

> But when I gdb the core file on customer server where the core file was
> created, I am able to get correct stack trace.
>
> Question, do I have to gdb the core file on the customer server to get
> correct stack trace? Any way to gdb the core file on my local server?

If you are using the same versions of the same programs/libraries, then
you will be able to inspect the corefile in your machine without
problems.

--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/