From: Daniel Jacobowitz <drow@false.org>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Use untested for macscp.exp if no macro information generated
Date: Sun, 01 Feb 2009 18:28:00 -0000 [thread overview]
Message-ID: <20090201182834.GE4597@caradoc.them.org> (raw)
In-Reply-To: <000001c9814b$919b63a0$b4d22ae0$@u-strasbg.fr>
On Wed, Jan 28, 2009 at 02:23:11PM +0100, Pierre Muller wrote:
>
> I tried to simplify my patch for macro support
> in order to get less uninteresting failures.
I think your earlier patch had the right idea. Why did it leave some
failures? We should have none if we're going to skip the test.
> if {[list_and_check_macro main WHERE {macscp1.c {before macscp1_3}}]} {
> - return 0
> + global verbose
> + set macro_support "unknown"
> + send_gdb "info source\n"
> + gdb_expect 10 {
General note, please use gdb_test_multiple. No need for a timeout in
most cases; use the default setting.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-02-01 18:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 11:37 Results of macscp.exp test on cygwin Pierre Muller
2008-10-09 16:29 ` Tom Tromey
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 [this message]
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=20090201182834.GE4597@caradoc.them.org \
--to=drow@false.org \
--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