|
Home > Archive > Unix Programming > January 2004 > Re: analyzing core dump
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: analyzing core dump
|
|
| aryzhov 2004-01-23, 4:49 pm |
| goutaman <member46288@mcse.ms> wrote in message news:<3539328.1067484957@mcse.ms>...quote:
> Hi,
>
> I am trying to analyze the core I got from production. The binary was
> generated ages ago and no one knows if it is a perfect fit to the
> current code.
>
> we want to try and generate the symbol table and run it along with the
> old binary in gdb.
>
>
>
> can anyone tell me how i can generate a symbol file from the code.
>
> ( idont want to generate a complete binary with the -g option
> and do it)
>
You can backtrace the stack and see the symbolic names of the functions,
if the binary is not striped. IMHO, there's nothing much more you can see,
anyway, without recompiling the code with -g.
Use $C macro in adb or bt command in gdb
adb BINARY_FILE CORE_FILE
or
gdb BINARY_FILE CORE_FILE
Regards,
Andrei
| |
| aryzhov 2004-01-23, 4:49 pm |
| goutaman <member46288@mcse.ms> wrote in message news:<3539328.1067484957@mcse.ms>...quote:
> Hi,
>
> I am trying to analyze the core I got from production. The binary was
> generated ages ago and no one knows if it is a perfect fit to the
> current code.
>
> we want to try and generate the symbol table and run it along with the
> old binary in gdb.
>
>
>
> can anyone tell me how i can generate a symbol file from the code.
>
> ( idont want to generate a complete binary with the -g option
> and do it)
>
You can backtrace the stack and see the symbolic names of the functions,
if the binary is not striped. IMHO, there's nothing much more you can see,
anyway, without recompiling the code with -g.
Use $C macro in adb or bt command in gdb
adb BINARY_FILE CORE_FILE
or
gdb BINARY_FILE CORE_FILE
Regards,
Andrei
| |
| aryzhov 2004-01-23, 4:59 pm |
| goutaman <member46288@mcse.ms> wrote in message news:<3539328.1067484957@mcse.ms>...quote:
> Hi,
>
> I am trying to analyze the core I got from production. The binary was
> generated ages ago and no one knows if it is a perfect fit to the
> current code.
>
> we want to try and generate the symbol table and run it along with the
> old binary in gdb.
>
>
>
> can anyone tell me how i can generate a symbol file from the code.
>
> ( idont want to generate a complete binary with the -g option
> and do it)
>
You can backtrace the stack and see the symbolic names of the functions,
if the binary is not striped. IMHO, there's nothing much more you can see,
anyway, without recompiling the code with -g.
Use $C macro in adb or bt command in gdb
adb BINARY_FILE CORE_FILE
or
gdb BINARY_FILE CORE_FILE
Regards,
Andrei
| |
| aryzhov 2004-01-23, 5:14 pm |
| goutaman <member46288@mcse.ms> wrote in message news:<3539328.1067484957@mcse.ms>...quote:
> Hi,
>
> I am trying to analyze the core I got from production. The binary was
> generated ages ago and no one knows if it is a perfect fit to the
> current code.
>
> we want to try and generate the symbol table and run it along with the
> old binary in gdb.
>
>
>
> can anyone tell me how i can generate a symbol file from the code.
>
> ( idont want to generate a complete binary with the -g option
> and do it)
>
You can backtrace the stack and see the symbolic names of the functions,
if the binary is not striped. IMHO, there's nothing much more you can see,
anyway, without recompiling the code with -g.
Use $C macro in adb or bt command in gdb
adb BINARY_FILE CORE_FILE
or
gdb BINARY_FILE CORE_FILE
Regards,
Andrei
|
|
|
|
|