From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: <gdb-patches@sourceware.org>
Subject: Re: Results of macscp.exp test on cygwin
Date: Thu, 09 Oct 2008 16:29:00 -0000 [thread overview]
Message-ID: <m38wsxvin8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <011801c92a03$4b71afa0$e2550ee0$@u-strasbg.fr> (Pierre Muller's message of "Thu\, 9 Oct 2008 13\:36\:39 +0200")
>>>>> "Pierre" == Pierre Muller <muller@ics.u-strasbg.fr> writes:
Pierre> Shouldn't we force dwarf-2 debug format, or at least
Pierre> skip the test if only stabs format is available?
Seems like a decent idea to me.
Pierre> FAIL: gdb.base/macscp.exp: c99 varargs expansion
[...]
Pierre> These failures are all due to the fact that stderr
Pierre> is itself a macro in cygwin that is expanded into
Pierre> "((__getreent())->_stderr)".
These tests don't really require the use of fprintf or stderr -- any
arbitrary identifier is fine. I'm testing this patch, which changes
these names.
Ok if it passes testing?
Tom
:ADDPATCH testsuite:
2008-10-09 Tom Tromey <tromey@redhat.com>
* gdb.base/macscp.exp: Use 'vafunc' and 'fixedarg' rather than
'fprintf' and 'stderr'.
diff --git a/gdb/testsuite/gdb.base/macscp.exp b/gdb/testsuite/gdb.base/macscp.exp
index 2a43a28..40546f9 100644
--- a/gdb/testsuite/gdb.base/macscp.exp
+++ b/gdb/testsuite/gdb.base/macscp.exp
@@ -566,44 +566,44 @@ gdb_test "macro expand SPLICE(robot, invasion)" \
# Varargs tests.
-gdb_test "macro define va_c99(...) fprintf (stderr, __VA_ARGS__)" \
+gdb_test "macro define va_c99(...) varfunc (fixedarg, __VA_ARGS__)" \
"" \
"define first varargs helper"
-gdb_test "macro define va2_c99(x, y, ...) fprintf (stderr, x, y, __VA_ARGS__)" \
+gdb_test "macro define va2_c99(x, y, ...) varfunc (fixedarg, x, y, __VA_ARGS__)" \
"" \
"define second varargs helper"
-gdb_test "macro define va_gnu(args...) fprintf (stderr, args)" \
+gdb_test "macro define va_gnu(args...) varfunc (fixedarg, args)" \
"" \
"define third varargs helper"
-gdb_test "macro define va2_gnu(args...) fprintf (stderr, ## args)" \
+gdb_test "macro define va2_gnu(args...) varfunc (fixedarg, ## args)" \
"" \
"define fourth varargs helper"
gdb_test "macro expand va_c99(one, two, three)" \
- "expands to: *fprintf \\(stderr, *one, two, three\\)" \
+ "expands to: *varfunc \\(fixedarg, *one, two, three\\)" \
"c99 varargs expansion"
gdb_test "macro expand va_c99()" \
- "expands to: *fprintf \\(stderr, *\\)" \
+ "expands to: *varfunc \\(fixedarg, *\\)" \
"c99 varargs expansion without an argument"
gdb_test "macro expand va2_c99(one, two, three, four)" \
- "expands to: *fprintf \\(stderr, *one, two, three, four\\)" \
+ "expands to: *varfunc \\(fixedarg, *one, two, three, four\\)" \
"c99 varargs expansion, multiple formal arguments"
gdb_test "macro expand va_gnu(one, two, three, four)" \
- "expands to: *fprintf \\(stderr, *one, two, three, four\\)" \
+ "expands to: *varfunc \\(fixedarg, *one, two, three, four\\)" \
"gnu varargs expansion"
gdb_test "macro expand va_gnu()" \
- "expands to: *fprintf \\(stderr, *\\)" \
+ "expands to: *varfunc \\(fixedarg, *\\)" \
"gnu varargs expansion without an argument"
gdb_test "macro expand va2_gnu()" \
- "expands to: *fprintf \\(stderr\\)" \
+ "expands to: *varfunc \\(fixedarg\\)" \
"gnu varargs expansion special splicing without an argument"
# Stringification tests.
next prev parent reply other threads:[~2008-10-09 16:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 11:37 Pierre Muller
2008-10-09 16:29 ` Tom Tromey [this message]
2008-10-09 16:46 ` Pedro Alves
2008-10-09 18:14 ` Daniel Jacobowitz
2008-10-09 20:21 ` Michael Snyder
2008-10-09 22:28 ` Paul Pluzhnikov
2008-10-10 16:04 ` [RFC] " Pierre Muller
2009-01-26 9:13 ` [PING] " Pierre Muller
2009-01-28 13:32 ` [RFC] Use untested for macscp.exp if no macro information generated Pierre Muller
2009-02-01 18:28 ` Daniel Jacobowitz
2009-02-03 14:36 ` [RFC-v2] " Pierre Muller
2009-02-18 22:59 ` [PING] " Pierre Muller
2009-02-19 8:20 ` Tom Tromey
2009-02-20 10:08 ` Pierre Muller
2009-05-11 11:30 ` PING : " Pierre Muller
2009-05-29 23:40 ` Tom Tromey
2009-05-30 8:04 ` Pierre Muller
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=m38wsxvin8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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