From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Testsuite regression for gdb.gdb/selftest.exp [Re: RFC: call bfd_init]
Date: Mon, 21 Jan 2013 20:40:00 -0000 [thread overview]
Message-ID: <20130121203948.GA27977@host2.jankratochvil.net> (raw)
In-Reply-To: <87hama30le.fsf@fleche.redhat.com>
On Mon, 21 Jan 2013 18:30:37 +0100, Tom Tromey wrote:
> >>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
> Tom> bfd_init is a no-op, so right now nothing notices. But, I figured it
> Tom> would be safe to add the call in case this ever changes.
>
> I'm checking this in now.
dbd454a9c7690a87c57d5b8a28a02388665c1f46 is the first bad commit
commit dbd454a9c7690a87c57d5b8a28a02388665c1f46
Author: Tom Tromey <tromey@redhat.com>
Date: Mon Jan 21 17:32:09 2013 +0000
* main.c (captured_main): Call bfd_init.
Running gdb/testsuite/gdb.gdb/selftest.exp ...
[...]
PASS: gdb.gdb/selftest.exp: next over textdomain PACKAGE
-PASS: gdb.gdb/selftest.exp: next over cmdarg_s VEC_cleanup
-PASS: gdb.gdb/selftest.exp: next over dirsize initialization
+FAIL: gdb.gdb/selftest.exp: unknown source line after next over textdomain PACKAGE
PASS: gdb.gdb/selftest.exp: print a string
-PASS: gdb.gdb/selftest.exp: step into xmalloc call
+FAIL: gdb.gdb/selftest.exp: step into xmalloc call
PASS: gdb.gdb/selftest.exp: xgdb is at prompt
PASS: gdb.gdb/selftest.exp: Set xgdb prompt
PASS: gdb.gdb/selftest.exp: send ^C to child process
Regards,
Jan
next prev parent reply other threads:[~2013-01-21 20:40 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 ` Jan Kratochvil [this message]
2013-01-21 20:45 ` Testsuite regression for gdb.gdb/selftest.exp [Re: RFC: call bfd_init] Tom Tromey
2013-01-22 15:47 ` 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=20130121203948.GA27977@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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