From: Daniel Jacobowitz <drow@mvista.com>
To: Pierre Habraken <Pierre.Habraken@imag.fr>
Cc: binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Expansing macro-definitions in Gas using Gdb
Date: Wed, 28 Aug 2002 05:50:00 -0000 [thread overview]
Message-ID: <20020828125130.GA15090@nevyn.them.org> (raw)
In-Reply-To: <3D6CC5AB.C4CA2B1E@imag.fr>
On Wed, Aug 28, 2002 at 02:44:27PM +0200, Pierre Habraken wrote:
> Hello,
>
> I would like to be able to display the value of #defined constants
> (C macro-definitions) #included in assembly language modules.
> The source files of these modules have suffix ".S" and are assembled
> using gcc.
> Using latest snapshots of gdb, it is possible to expand
> macro-definitions included in C source files compiled with gcc.
> However this does not appear to work for assembly source files.
> Is it possible to force gas (or gcc) to put the required data into the
> object file ?
Not really. If you use a C file and asm("") constructs, you can get
the macros; otherwise, you can probably get them by linking a dummy .c
file in your project which includes all of the headers.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-08-28 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 5:44 Pierre Habraken
2002-08-28 5:50 ` Daniel Jacobowitz [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=20020828125130.GA15090@nevyn.them.org \
--to=drow@mvista.com \
--cc=Pierre.Habraken@imag.fr \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.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