This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: Fwd: Decompiler program

From: "Robert Norton" <rnorton at broadcom dot com>
To: "Prasanna .S" <myprasanna at gmail dot com>, gdb at sourceware dot org
Date: Mon, 10 Sep 2007 02:48:20 -0700
Subject: RE: Fwd: Decompiler program
References: <1a47b9f10709061414m3344094m1f9da016cf1f765c@mail.gmail.com> <1a47b9f10709061417t6a8778bboe741ecbe31c2b0eb@mail.gmail.com> <1a47b9f10709061418h4b60ed07od05d07718e4809b5@mail.gmail.com> <46E0732F.7060309@adacore.com> <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

References:
- Fwd: Decompiler program
  - From: Prasanna .S
- Re: Fwd: Decompiler program
  - From: Prasanna .S

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]