Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: gdb-patches@sources.redhat.com
Subject: macro-expanding expressions in GDB
Date: Thu, 07 Jun 2001 08:47:00 -0000	[thread overview]
Message-ID: <npn17k1eag.fsf_-_@zwingli.cygnus.com> (raw)
In-Reply-To: <87g0dc7u5w.fsf@cgsoftware.com>

Daniel Berlin <dan@cgsoftware.com> writes:
> Speaking of real parsers, i've hooked up GCC's cpplib to GDB's c
> expression parser if anyone is interested in the work.  I'll
> eventually submit it once the hooks to do the necessary gdb lookups to
> handle macros are done.  Neil said he'd try to have something

This is a feature to die for.  Fantastic.

I have two concerns about using cpplib:
- I don't want GDB builds to require the GCC sources around.  This is
  mostly bureacracy --- we'd need to have cpplib moved into its own
  top-level directory, so we could share it with GCC.
- I wonder how much of cpplib we actually need.  We don't need
  #includes, #ifs, or CPP expression evaluation.  cpplib seems
  heavyweight.  This is somewhat nitpicky.

Sorry, which Niel?  If I can find the bandwidth, I'd love to do the
symbol table support for this.

> I also submitted patches to gcc to make it produce the dwarf2 macro
> info necessary for us to let the user use macros from GDB that are
> used in the source.

And we don't even need to wait for that.  We can add the macro info to
the .s files manually, and test against those files.


  parent reply	other threads:[~2001-06-07  8:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22 14:06 [RFA] linespec.c change to stop "malformed template specification" error Daniel Berlin
2001-06-06 16:09 ` Elena Zannoni
2001-06-06 17:00   ` Fernando Nasser
2001-06-06 21:00   ` Jim Blandy
2001-06-06 22:09     ` Daniel Berlin
2001-06-07  8:40       ` Jim Blandy
2001-06-07  8:47       ` Jim Blandy [this message]
2001-06-07  9:01         ` macro-expanding expressions in GDB Daniel Berlin
2001-06-07 11:52           ` Jim Blandy
2001-06-07 12:04             ` Daniel Berlin
2001-06-07 11:16         ` Stan Shebs
2001-06-06 23:36     ` [RFA] linespec.c change to stop "malformed template specification" error Daniel Berlin
2001-06-07  6:00     ` Fernando Nasser
2001-06-07  9:09       ` Jim Blandy
2001-06-07  7:40     ` Elena Zannoni
     [not found]       ` <nppucg1eq5.fsf@zwingli.cygnus.com>
2001-06-07  9:13         ` Daniel Berlin
2001-06-07 11:18           ` Jim Blandy
2001-06-07 11:35             ` Daniel Berlin
2001-06-07 15:22               ` Jim Blandy
2001-06-07 16:40                 ` Daniel Berlin
2001-06-07 10:27         ` Elena Zannoni
2001-06-07 12:30           ` Fernando Nasser
2001-06-07 15:14           ` Jim Blandy

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=npn17k1eag.fsf_-_@zwingli.cygnus.com \
    --to=jimb@zwingli.cygnus.com \
    --cc=dan@cgsoftware.com \
    --cc=gdb-patches@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