From: "Prasanna .S" <myprasanna@gmail.com>
To: gdb@sourceware.org
Subject: Fwd: Decompiler program
Date: Thu, 06 Sep 2007 21:33:00 -0000 [thread overview]
Message-ID: <1a47b9f10709061418h4b60ed07od05d07718e4809b5@mail.gmail.com> (raw)
In-Reply-To: <1a47b9f10709061417t6a8778bboe741ecbe31c2b0eb@mail.gmail.com>
Hi,
I am a student in India. I am not very experienced with gdb's
internals but have used it before.
Broadly i am interested in writing a decompiler
(given a binary, create some readable HLL code), that let's you trace
through code.
I've used gdb to step through binaries without debug info, but as far
as i've known (or tried),
it has a limitation that it cant step out of a proc that it doesnt
have src (or debug info to).
So i cant step into libraries (am i correct?)
So all i want to know is a broad idea about the complexity involved in
writing a decompiler using
some of gcc's C libs, that can parse the ELF binary (i think i've seen
a lib for this parsing part in gcc)
and generate dis-assembly that can be traced freely. (Ofcourse the ELF
binary has to assumed to
contain no debug info).
Thanks a lot for sparing your time,
-Prasanna
next parent reply other threads:[~2007-09-06 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1a47b9f10709061414m3344094m1f9da016cf1f765c@mail.gmail.com>
[not found] ` <1a47b9f10709061417t6a8778bboe741ecbe31c2b0eb@mail.gmail.com>
2007-09-06 21:33 ` Prasanna .S [this message]
2007-09-06 21:48 ` Joel Brobecker
[not found] ` <46E0732F.7060309@adacore.com>
2007-09-07 13:53 ` Prasanna .S
2007-09-10 15:49 ` Robert Norton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1a47b9f10709061418h4b60ed07od05d07718e4809b5@mail.gmail.com \
--to=myprasanna@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox