Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: Daniel Berlin <dan@dberlin.org>, Jim Blandy <jimb@redhat.com>,
	gdb-patches@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: RFC: C/C++ preprocessor macro support for GDB
Date: Mon, 18 Mar 2002 11:45:00 -0000	[thread overview]
Message-ID: <3C9643B8.334D7812@apple.com> (raw)
In-Reply-To: <20020318184525.GC19897@daikokuya.demon.co.uk>

Neil Booth wrote:
> 
> [...]  We should have GCC and GDB agree
> perfectly on macro expansion, otherwise there is little point.

As someone who has had much of his time consumed by keeping
another preprocessor (Apple's cpp-precomp) in sync with GNU cpp,
I think we really should try hard to avoid duplicate macro
expanders.

The hallmark of a good expression evaluator in the debugger is
that it passes the "cut-n-paste" test, that is, you can take any
chunk of program source code and have the debugger produce the
same result as the compiler.  This is an ideal, and very hard to
accomplish everywhere, but if the debugger uses the compiler's
own preprocessing library, it gets a long way there with just
the one step.

I also imagine the extreme puzzlement of a GDB user who spends
an hour trying to figure why stepping always goes down the else
clause, when the evaluation of the if condition clearly shows the
result is true - because the if condition includes a macro that
was expanded differently...

Stan


  reply	other threads:[~2002-03-18 19:45 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 [this message]
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=3C9643B8.334D7812@apple.com \
    --to=shebs@apple.com \
    --cc=dan@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=neil@daikokuya.demon.co.uk \
    /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