From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: Regression: [Re: RFC: change "program exited" message]
Date: Tue, 08 Mar 2011 15:11:00 -0000 [thread overview]
Message-ID: <m3zkp5iscv.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110308065419.GA1239@host1.jankratochvil.net> (Jan Kratochvil's message of "Tue, 8 Mar 2011 07:54:19 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> This has a heavy regression for me such as:
Jan> FAIL: gdb.base/break.exp: continue until exit at recursive next test (the program exited)
I will fix it.
Jan> But this is not enough for all the regressions. I do not
Jan> understand how it could pass the testsuite for you.
Maybe the tester has a bug.
I should probably switch it to use your comparison script, so that we
are more in sync.
Tom
next prev parent reply other threads:[~2011-03-08 14:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 20:52 RFC: change "program exited" message Tom Tromey
2011-03-03 21:18 ` Michael Snyder
2011-03-03 21:20 ` Pedro Alves
2011-03-04 7:37 ` Eli Zaretskii
2011-03-04 17:24 ` Tom Tromey
2011-03-04 19:13 ` Pedro Alves
2011-03-04 19:23 ` Tom Tromey
2011-03-04 19:38 ` Pedro Alves
2011-03-07 16:17 ` Tom Tromey
2011-03-08 9:43 ` Regression: [Re: RFC: change "program exited" message] Jan Kratochvil
2011-03-08 15:11 ` Tom Tromey [this message]
2011-03-09 14:37 ` Tom Tromey
2011-03-09 16:22 ` Jan Kratochvil
2011-03-09 16:29 ` Joel Brobecker
2011-03-09 17:28 ` Tom Tromey
2011-03-09 17:32 ` Jan Kratochvil
2011-03-09 18:15 ` Tom Tromey
2011-03-09 18:22 ` Jan Kratochvil
2011-03-09 18:58 ` Tom Tromey
2011-03-04 9:12 ` RFC: change "program exited" message Mark Kettenis
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=m3zkp5iscv.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pedro@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