From: "Robert Norton" <rnorton@broadcom.com>
To: "Prasanna .S" <myprasanna@gmail.com>, gdb@sourceware.org
Subject: RE: Fwd: Decompiler program
Date: Mon, 10 Sep 2007 15:49:00 -0000 [thread overview]
Message-ID: <B0D822BFECD50F4991F2516EA50F273C02609C29@NT-IRVA-0752.brcm.ad.broadcom.com> (raw)
In-Reply-To: <1a47b9f10709070637i2bdb4f7aw48d37680fcf4b809@mail.gmail.com>
> -----Original Message-----
> From: gdb-owner@sourceware.org
> [mailto:gdb-owner@sourceware.org] On Behalf Of Prasanna .S
> Sent: 07 September 2007 14:37
> To: gdb@sourceware.org
> Subject: Re: Fwd: Decompiler program
> More precisely can you trace through instruction by instruction
> emitted by objdump,
> by a objdump/gdb lib combination?
Have you tried the 'disassemble' (also x/i <address>) command in gdb? It
provides disassembly of the current function or of a given range of
addresses. Perhaps this, combined with the nexti / stepi commands, will
allow you to trace execution at assembly level? Turning this into HLL
code using decompilation techniques (via a 'decompile' command) would be
an interesting feature.
My apologies if I have misundertsood what you are asking for.
Robert
prev parent reply other threads:[~2007-09-10 9:49 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
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 [this message]
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=B0D822BFECD50F4991F2516EA50F273C02609C29@NT-IRVA-0752.brcm.ad.broadcom.com \
--to=rnorton@broadcom.com \
--cc=gdb@sourceware.org \
--cc=myprasanna@gmail.com \
/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