From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gdb-patches@sourceware.org, Kevin Buettner <kevinb@redhat.com>
Subject: Testsuite regression for annota1.exp and annota3.exp [Re: [PATCH] [SH] ... can do this signal stuff!]
Date: Tue, 28 Feb 2012 16:05:00 -0000 [thread overview]
Message-ID: <20120228160351.GA12029@host2.jankratochvil.net> (raw)
In-Reply-To: <874nub5n16.fsf@schwinge.name>
On Tue, 28 Feb 2012 10:23:49 +0100, Thomas Schwinge wrote:
> gdb/testsuite/
> 2012-02-28 Thomas Schwinge <thomas@codesourcery.com>
>
> * gdb.base/annota1.c [__sh__]: Remove any special-casing.
> * gdb.base/annota3.c: Likewise.
> * gdb.base/sigall.c: Likewise.
> * gdb.base/signals.c: Likewise.
> * gdb.reverse/sigall-reverse.c: Likewise.
Sorry but it caused regressions. Please use gdb_get_line_number there.
Thanks,
Jan
-PASS: gdb.base/annota1.exp: breakpoint info
-PASS: gdb.base/annota1.exp: run until main breakpoint
+FAIL: gdb.base/annota1.exp: breakpoint info (timeout)
+FAIL: gdb.base/annota1.exp: run until main breakpoint (timeout)
-PASS: gdb.base/annota1.exp: break at 28
+FAIL: gdb.base/annota1.exp: break at 28 (timeout)
-PASS: gdb.base/annota1.exp: annotate ignore count change
-PASS: gdb.base/annota1.exp: breakpoint ignore count
+FAIL: gdb.base/annota1.exp: annotate ignore count change (timeout)
+FAIL: gdb.base/annota1.exp: next to exit loop (timeout)
+FAIL: gdb.base/annota1.exp: breakpoint ignore count (timeout)
-PASS: gdb.base/annota1.exp: signal sent
-PASS: gdb.base/annota1.exp: cleanup core file (removed)
+FAIL: gdb.base/annota1.exp: signal sent (timeout)
+PASS: gdb.base/annota1.exp: cleanup core file (not dumped)
-PASS: gdb.base/annota3.exp: breakpoint info
-PASS: gdb.base/annota3.exp: run until main breakpoint
+FAIL: gdb.base/annota3.exp: breakpoint info (pattern 3 + sentinel)
+FAIL: gdb.base/annota3.exp: run until main breakpoint (pattern 8)
-PASS: gdb.base/annota3.exp: break at 28
+FAIL: gdb.base/annota3.exp: break at 28 (pattern 2 + sentinel)
-PASS: gdb.base/annota3.exp: annotate ignore count change
-PASS: gdb.base/annota3.exp: next to exit loop
-PASS: gdb.base/annota3.exp: breakpoint ignore count
-PASS: gdb.base/annota3.exp: get inferior pid
-PASS: gdb.base/annota3.exp: signal sent
-PASS: gdb.base/annota3.exp: cleanup core file (removed)
+FAIL: gdb.base/annota3.exp: annotate ignore count change (pattern 2)
+FAIL: gdb.base/annota3.exp: next to exit loop (pattern 2)
+FAIL: gdb.base/annota3.exp: breakpoint ignore count (pattern 2)
+FAIL: gdb.base/annota3.exp: get inferior pid (timeout)
+FAIL: gdb.base/annota3.exp: signal sent (pattern 2)
+PASS: gdb.base/annota3.exp: cleanup core file (not dumped)
next prev parent reply other threads:[~2012-02-28 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 10:03 [PATCH] [SH] ... can do this signal stuff! Thomas Schwinge
2012-02-28 13:43 ` Pedro Alves
2012-02-28 16:05 ` Jan Kratochvil [this message]
2012-02-28 19:42 ` Testsuite regression for annota1.exp and annota3.exp [Re: [PATCH] [SH] ... can do this signal stuff!] Thomas Schwinge
2012-02-28 19:43 ` Jan Kratochvil
2012-02-28 23:27 ` Thomas Schwinge
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=20120228160351.GA12029@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=thomas@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