From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Vladimir Prus <vladimir@codesourcery.com>
Subject: Re: [RFA] fix *stopped for CLI commands
Date: Sun, 15 Feb 2009 18:22:00 -0000 [thread overview]
Message-ID: <200902151547.28642.pedro@codesourcery.com> (raw)
In-Reply-To: <200902142222.31325.vladimir@codesourcery.com>
Oops, I'm seeing this:
Running ../../../src/gdb/testsuite/gdb.gdb/observer.exp ...
FAIL: gdb.gdb/observer.exp: second observer attached; check second observer counter value
FAIL: gdb.gdb/observer.exp: 1st observer added; check first observer counter value
FAIL: gdb.gdb/observer.exp: 2nd observer added; check first observer counter value
FAIL: gdb.gdb/observer.exp: 2nd observer added; check second observer counter value
FAIL: gdb.gdb/observer.exp: 3rd observer added; check first observer counter value
FAIL: gdb.gdb/observer.exp: 3rd observer added; check second observer counter value
FAIL: gdb.gdb/observer.exp: 3rd observer added; check third observer counter value
FAIL: gdb.gdb/observer.exp: 2nd observer removed; check first observer counter value
FAIL: gdb.gdb/observer.exp: 2nd observer removed; check third observer counter value
FAIL: gdb.gdb/observer.exp: 1st observer removed; check third observer counter value
FAIL: gdb.gdb/observer.exp: three observers added; check first observer counter value
FAIL: gdb.gdb/observer.exp: three observers added; check second observer counter value
FAIL: gdb.gdb/observer.exp: three observers added; check third observer counter value
FAIL: gdb.gdb/observer.exp: third observer removed; check first observer counter value
FAIL: gdb.gdb/observer.exp: third observer removed; check second observer counter value
FAIL: gdb.gdb/observer.exp: second observer removed; check first observer counter value
Due to:
(gdb) PASS: gdb.gdb/observer.exp: second observer attached; reset third observer counter
call observer_notify_normal_stop (0)
Too few arguments in function call.
(gdb) PASS: gdb.gdb/observer.exp: second observer attached; sending notification
(outch, that should have been a FAIL)
The test needs to be adjusted to the new extra argument this
notification takes.
Alternatively, we could use a safer and more future proof test specific
notification in doc/observer.texi, instead of reusing the normal_stop
notification. Say,
@deftypefun void test_notification (int @var{somearg})
For internal testing. Do not use. See testsuite/gdb.gdb/observer.exp.
@end deftypefun
--
Pedro Alves
next prev parent reply other threads:[~2009-02-15 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 7:44 Vladimir Prus
2009-02-06 21:11 ` Tom Tromey
2009-02-07 1:04 ` Joel Brobecker
2009-02-12 8:46 ` Vladimir Prus
2009-02-12 20:37 ` Eli Zaretskii
2009-02-14 20:43 ` Vladimir Prus
2009-02-15 18:22 ` Pedro Alves [this message]
2009-02-17 19:25 ` Vladimir Prus
2009-02-17 19:29 ` Pedro Alves
2009-02-09 20:36 ` Daniel Jacobowitz
2009-02-10 20:50 ` Marc Khouzam
2009-02-10 20:58 ` Vladimir Prus
2009-02-11 14:09 ` Marc Khouzam
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=200902151547.28642.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@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