public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Disassemble binary with Debug info
@ 2008-02-12 15:14 Wombat
  2008-02-12 15:44 ` Andrew Haley
  2008-02-12 15:47 ` David Daney
  0 siblings, 2 replies; 4+ messages in thread
From: Wombat @ 2008-02-12 15:14 UTC (permalink / raw)
  To: gcc-help

Hello
I recently recovered an old ELF binary of mine which had been compiled 
(probably) with GCC2. Unfortunetally, I do not have the source code 
anymore, but the binary contains the debug information.Using objdump 
--debugging, I could get all my typedefs, however I'd like to view the 
the whole code. I would be very happy if anyone could point me to a 
Disassembler that uses the debug information to name variables, 
especially variables inside structs. objdump --disassemble does not seem 
to that.
So I'm kind of stuck, any help is welcome

Thank you

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Disassemble binary with Debug info
  2008-02-12 15:14 Disassemble binary with Debug info Wombat
@ 2008-02-12 15:44 ` Andrew Haley
  2008-02-12 15:47 ` David Daney
  1 sibling, 0 replies; 4+ messages in thread
From: Andrew Haley @ 2008-02-12 15:44 UTC (permalink / raw)
  To: Wombat; +Cc: gcc-help

Wombat wrote:
> Hello
> I recently recovered an old ELF binary of mine which had been compiled 
> (probably) with GCC2. Unfortunetally, I do not have the source code 
> anymore, but the binary contains the debug information.Using objdump 
> --debugging, I could get all my typedefs, however I'd like to view the 
> the whole code. I would be very happy if anyone could point me to a 
> Disassembler that uses the debug information to name variables, 
> especially variables inside structs. objdump --disassemble does not seem 
> to that.
> So I'm kind of stuck, any help is welcome

readelf --debug will do it, but the output is not easy to read.

Andrew.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Disassemble binary with Debug info
  2008-02-12 15:14 Disassemble binary with Debug info Wombat
  2008-02-12 15:44 ` Andrew Haley
@ 2008-02-12 15:47 ` David Daney
  2008-02-12 17:35   ` Wombat
  1 sibling, 1 reply; 4+ messages in thread
From: David Daney @ 2008-02-12 15:47 UTC (permalink / raw)
  To: Wombat; +Cc: gcc-help

Wombat wrote:
> Hello
> I recently recovered an old ELF binary of mine which had been compiled 
> (probably) with GCC2. Unfortunetally, I do not have the source code 
> anymore, but the binary contains the debug information.Using objdump 
> --debugging, I could get all my typedefs, however I'd like to view the 
> the whole code. I would be very happy if anyone could point me to a 
> Disassembler that uses the debug information to name variables, 
> especially variables inside structs. objdump --disassemble does not 
> seem to that.
> So I'm kind of stuck, any help is welcome
>
> Thank you
If it really contains full debugging information, you can load it into 
gdb and use ptype and friends to print the definitions of all types.

David Daney

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Disassemble binary with Debug info
  2008-02-12 15:47 ` David Daney
@ 2008-02-12 17:35   ` Wombat
  0 siblings, 0 replies; 4+ messages in thread
From: Wombat @ 2008-02-12 17:35 UTC (permalink / raw)
  To: gcc-help

David Daney schrieb:
> If it really contains full debugging information, you can load it into 
> gdb and use ptype and friends to print the definitions of all types.
>
> David Daney
>
>
Yeah, that's what I already got with objdump. It gave me all typedefs in 
one text file.
What I want is a Disassembler or Debugger that actually uses this 
information to make the assembler code more readable.
I mean, from the objdump output, I can see that the debug information 
holds all variable's names and their type. The types themselves (if 
custom) are also defined. Therefore, a disassembler could use that to 
make the code easier to read.
Do you see what I mean?

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-02-12 17:35 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-12 15:14 Disassemble binary with Debug info Wombat
2008-02-12 15:44 ` Andrew Haley
2008-02-12 15:47 ` David Daney
2008-02-12 17:35   ` Wombat

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).