From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix macro expansion bug
Date: Thu, 11 Dec 2008 23:28:00 -0000 [thread overview]
Message-ID: <m3skoub8g3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200812112304.39302.pedro@codesourcery.com> (Pedro Alves's message of "Thu\, 11 Dec 2008 23\:04\:38 +0000")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> Though, I'm having a bit of trouble convincing myself that the logic to
Pedro> handle 'pp-number e|E|p|P|. sign' below is 100% sane.
[...]
Pedro> It seems macro_is_identifier_nondigit will always eat any of "eEpP",
Pedro> thus, say, when parsing "1e-" only "1e" will be identified as a pp
Pedro> number, leaving "+" in the stream. Is this right?
Yeah. Also, "." should not appear in the strchr argument.
Here's a new patch. I'll regression-test it. I don't expect
problems. Ok if it passes?
>> + "expands to: siginfo. fields.fault.si_addr" \
Pedro> Just curious, as it's just a visual annoyance: do you know where
Pedro> this space comes from? Do we store the definition with the space for
Pedro> some reason? We don't get that extra space if the define came
Pedro> from the code, instead of from a 'macro define'.
Yes, it is a bug in "macro define".
I'll fix shortly.
Tom
2008-12-11 Tom Tromey <tromey@redhat.com>
* macroexp.c (get_pp_number): Require digit after leading ".".
Correctly handle suffixes.
2008-12-11 Tom Tromey <tromey@redhat.com>
* gdb.base/macscp.exp: New regression test.
diff --git a/gdb/macroexp.c b/gdb/macroexp.c
index 7fb23ce..dda3592 100644
--- a/gdb/macroexp.c
+++ b/gdb/macroexp.c
@@ -278,20 +278,22 @@ get_pp_number (struct macro_buffer *tok, char *p, char *end)
{
if (p < end
&& (macro_is_digit (*p)
- || *p == '.'))
+ || (*p == '.'
+ && p + 2 <= end
+ && macro_is_digit (p[1]))))
{
char *tok_start = p;
while (p < end)
{
- if (macro_is_digit (*p)
- || macro_is_identifier_nondigit (*p)
- || *p == '.')
- p++;
- else if (p + 2 <= end
- && strchr ("eEpP.", *p)
- && (p[1] == '+' || p[1] == '-'))
+ if (p + 2 <= end
+ && strchr ("eEpP", *p)
+ && (p[1] == '+' || p[1] == '-'))
p += 2;
+ else if (macro_is_digit (*p)
+ || macro_is_identifier_nondigit (*p)
+ || *p == '.')
+ p++;
else
break;
}
diff --git a/gdb/testsuite/gdb.base/macscp.exp b/gdb/testsuite/gdb.base/macscp.exp
index 9cb9ef5..40021b9 100644
--- a/gdb/testsuite/gdb.base/macscp.exp
+++ b/gdb/testsuite/gdb.base/macscp.exp
@@ -652,3 +652,11 @@ gdb_test "print str(maude)" \
gdb_test "print xstr(maude)" \
" = \"5\"" \
"stringify with substitution"
+
+# Regression test for pp-number bug.
+gdb_test "macro define si_addr fields.fault.si_addr" \
+ "" \
+ "define si_addr macro"
+gdb_test "macro expand siginfo.si_addr" \
+ "expands to: siginfo. fields.fault.si_addr" \
+ "macro expand siginfo.si_addr"
next prev parent reply other threads:[~2008-12-11 23:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 21:37 Tom Tromey
2008-12-11 23:05 ` Pedro Alves
2008-12-11 23:28 ` Tom Tromey [this message]
2008-12-11 23:35 ` Pedro Alves
2008-12-12 17:07 ` Tom Tromey
2008-12-11 23:31 ` Andreas Schwab
2008-12-11 23:41 ` Tom Tromey
2008-12-11 23:51 ` Pedro Alves
2008-12-11 23:58 ` Tom Tromey
2008-12-12 17:02 ` Tom Tromey
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=m3skoub8g3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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