From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Testsuite regression for gdb.gdb/selftest.exp [Re: RFC: call bfd_init]
Date: Tue, 22 Jan 2013 15:47:00 -0000 [thread overview]
Message-ID: <87a9s1z0bx.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87ehhe1d09.fsf@fleche.redhat.com> (Tom Tromey's message of "Mon, 21 Jan 2013 13:45:26 -0700")
Tom> Haha, of course.
Tom> I will fix it tomorrow.
Here is what I am checking in.
Tom> selftest.exp fails randomly for me so it is in my list to ignore.
Tom> I guess I will try to diagnose this as well.
It is due to differences in the builds. A comment in selftest.exp warns
about this, but the test names still depend on the details of the build.
Gross. Anyway I will stop ignoring it now.
Tom
2013-01-22 Tom Tromey <tromey@redhat.com>
* gdb.gdb/selftest.exp (do_steps_and_nexts): Handle bfd_init
call.
Index: gdb.gdb/selftest.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.gdb/selftest.exp,v
retrieving revision 1.32
diff -u -r1.32 selftest.exp
--- gdb.gdb/selftest.exp 1 Jan 2013 06:41:22 -0000 1.32
+++ gdb.gdb/selftest.exp 22 Jan 2013 15:46:10 -0000
@@ -150,6 +150,10 @@
set description "next over textdomain PACKAGE"
set command "next"
}
+ -re ".*bfd_init ..;.*$gdb_prompt $" {
+ set description "next over bfd_init"
+ set command "next"
+ }
-re ".*VEC_cleanup .cmdarg_s.*$gdb_prompt $" {
set description "next over cmdarg_s VEC_cleanup"
set command "next"
prev parent reply other threads:[~2013-01-22 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 15:18 RFC: call bfd_init Tom Tromey
2013-01-11 15:34 ` Joel Brobecker
2013-01-21 17:39 ` Tom Tromey
2013-01-21 20:40 ` Testsuite regression for gdb.gdb/selftest.exp [Re: RFC: call bfd_init] Jan Kratochvil
2013-01-21 20:45 ` Tom Tromey
2013-01-22 15:47 ` Tom Tromey [this message]
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=87a9s1z0bx.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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