From: Daniel Berlin <dan@dberlin.org>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com, <gcc@gcc.gnu.org>
Subject: Re: RFC: C/C++ preprocessor macro support for GDB
Date: Sun, 17 Mar 2002 16:53:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0203171948050.20662-100000@dberlin.org> (raw)
In-Reply-To: <6FD71526-39C9-11D6-A7C8-000393575BCC@dberlin.org>
On Sun, 17 Mar 2002, Daniel Berlin wrote:
>
> On Sunday, March 17, 2002, at 01:23 AM, Jim Blandy wrote:
>
> >
> > The following patch adds support for C/C++ preprocessor macros to GDB.
> > It's tentative:
> >
> > - There are no ChangeLog entries.
> > - It's not broken up into relatively independent changes.
> > - There's no documentation.
> > - There are no tests.
> > - There are some unimplemented features.
> >
> > I'll put it in proper form and re-post it soon, but I'm putting it out
> > now in hopes that folks will try it out and send me bug reports and
> > suggestions.
> >
> > The patch reads Dwarf 2 macro information, which GCC doesn't currently
> > generate. (In fact, I don't know if any compiler generates it at the
> > moment.)
For the record, I can name plenty of compilers that generate it.
Along with other dwarf2 features that gdb doesn't support yet (Intel's C++
compiler for linux generates namespaces and other things, fer instance).
>
> Umm, Actually, we've been generating it for quite a while.
> Try -gdwarf-2 -g3.
> I can't remember when exactly I added it, but it was certainly a while
> ago.
> > So the debugger side of pre-processor macro support is pretty much
> > done. I hope someone in GCC-land gets the itch and adds the
> > compiler-side support needed.
And Jim, in the future, if you are considering adding more support for
various debug info features, it would probably be better for you if you
asked if gcc had support before you started.
That way, you would save the time of having to make up your own test
cases by hand in assembly, etc, during development.
In this case, the libcpp people probably would have been willing to work
with you so you didn't have to write your own macro-expander.
--Dan
next prev parent reply other threads:[~2002-03-18 0:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 22:23 Jim Blandy
2002-03-17 0:11 ` Zack Weinberg
2002-03-17 19:33 ` Jim Blandy
2002-03-17 4:46 ` Neil Booth
2002-03-17 20:35 ` Jim Blandy
2002-03-17 23:29 ` Neil Booth
2002-03-18 0:06 ` Daniel Berlin
2002-03-18 0:36 ` Zack Weinberg
2002-03-18 5:00 ` Daniel Berlin
2002-03-18 5:32 ` Daniel Berlin
2002-03-18 11:18 ` Jim Blandy
2002-03-18 12:09 ` Neil Booth
2002-03-18 10:45 ` Neil Booth
2002-03-18 11:45 ` Stan Shebs
2002-03-18 12:05 ` Neil Booth
2002-03-18 12:19 ` Stan Shebs
2002-03-18 15:45 ` Jim Blandy
2002-03-18 7:16 ` Andrew Cagney
2002-03-17 9:07 ` Daniel Berlin
2002-03-17 16:53 ` Daniel Berlin [this message]
2002-03-18 7:35 ` Batons? Was: " Andrew Cagney
2002-03-18 12:08 ` Jim Blandy
2002-03-18 12:55 ` Andrew Cagney
2002-03-18 15:49 ` Jim Blandy
2002-03-18 7:39 ` Andrew Cagney
2002-03-19 13:16 ` Jim Blandy
2002-03-18 10:34 ` Neil Booth
2002-03-18 11:11 ` Neil Booth
2002-03-18 16:03 ` Jim Blandy
2002-03-18 17:42 ` Stan Shebs
2002-03-18 19:51 ` Jim Blandy
2002-03-18 23:23 ` Neil Booth
2002-03-18 20:33 ` Jim Blandy
2002-03-23 12:14 ` Andrew Cagney
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=Pine.LNX.4.44.0203171948050.20662-100000@dberlin.org \
--to=dan@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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