From: Zack Weinberg <zack@codesourcery.com>
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 00:11:00 -0000 [thread overview]
Message-ID: <20020317081117.GF896@codesourcery.com> (raw)
In-Reply-To: <20020317062306.CC96D5E9DE@zwingli.cygnus.com>
On Sun, Mar 17, 2002 at 01:23:06AM -0500, Jim Blandy wrote:
>
> 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.) I've tested it against some hand-written ".debug_macinfo"
> sections, which I'll post in the next message. So it's not actually
> useful yet.
Did you try -gdwarf-2 -g3 (i.e. level 3 of dwarf2 debug)? It's not
generated by default due to the space cost, but I think GCC will do
it.
zw
next prev parent reply other threads:[~2002-03-17 8:11 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 [this message]
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
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=20020317081117.GF896@codesourcery.com \
--to=zack@codesourcery.com \
--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