From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Remove pass in skip_unwinder_tests
Date: Fri, 24 Aug 2012 13:38:00 -0000 [thread overview]
Message-ID: <20120824133738.GB5219@host2.jankratochvil.net> (raw)
In-Reply-To: <1345715389-20955-2-git-send-email-yao@codesourcery.com>
On Thu, 23 Aug 2012 11:49:49 +0200, Yao Qi wrote:
> As we discussed, proc skip_unwinder_tests should not generate any FAIL
> or PASS in test summary,
During comparison across releases and testsuite modes it makes the diffs more
difficult to read:
Running gdb/testsuite/gdb.java/jnpe.exp ...
PASS: gdb.java/jnpe.exp: compilation jnpe.java
-FAIL: gdb.java/jnpe.exp: check for unwinder hook
PASS: gdb.java/jnpe.exp: disable SIGSEGV for next-over-NPE
PASS: gdb.java/jnpe.exp: next over NPE
-PASS: gdb.java/jnpe.exp: continue to success for next-over-NPE
+FAIL: gdb.java/jnpe.exp: continue to success for next-over-NPE
Has the last testcase regressed because the check "check for unwinder hook" is
therefore no longer there? Does it PASS or FAIL now? etc.
In other case:
#gdb.java/jnpe.exp
Running gdb/testsuite/gdb.java/jnpe.exp ...
PASS: gdb.java/jnpe.exp: compilation jnpe.java
-PASS: gdb.java/jnpe.exp: check for unwinder hook
PASS: gdb.java/jnpe.exp: disable SIGSEGV for next-over-NPE
PASS: gdb.java/jnpe.exp: next over NPE
FAIL: gdb.java/jnpe.exp: continue to success for next-over-NPE
It was clear before why the testcase failed - because its
'check for unwinder hook' PASSes which should not in RHEL-5 x86_64 -m32 mode
(as debuginfo from gcc libraries is missing there).
the testcase was doing:
(gdb) print _Unwind_DebugHook^M
$1 = {void(void, void)} 0x7ffff78d4a90 <_Unwind_DebugHook>^M
(gdb) PASS: gdb.java/jnpe.exp: check for unwinder hook
handle SIGSEGV nostop noprint^M
Signal Stop Print Pass to program Description^M
SIGSEGV No No Yes Segmentation fault^M
(gdb) PASS: gdb.java/jnpe.exp: disable SIGSEGV for next-over-NPE
Not is that "print _Unwind_DebugHook"
a part of the "disable SIGSEGV for next-over-NPE" test?
(gdb) print _Unwind_DebugHook^M
$1 = {void(void, void)} 0x7ffff78d4a90 <_Unwind_DebugHook>^M
(gdb) handle SIGSEGV nostop noprint^M
Signal Stop Print Pass to program Description^M
SIGSEGV No No Yes Segmentation fault^M
(gdb) PASS: gdb.java/jnpe.exp: disable SIGSEGV for next-over-NPE
I do not see removing of useful messages to be much improvement.
I understand it was checked in with a good intention.
Jan
next prev parent reply other threads:[~2012-08-24 13:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 16:20 RFC: consolidate checks for _Unwind_DebugHook in test suite Tom Tromey
2012-08-15 0:53 ` Yao Qi
2012-08-15 13:58 ` Tom Tromey
2012-08-22 14:26 ` Tom Tromey
2012-08-23 9:50 ` [PATCH 1/2] Append "." in error message Yao Qi
2012-08-23 9:50 ` [PATCH 2/2] Remove pass in skip_unwinder_tests Yao Qi
2012-08-23 10:52 ` Pedro Alves
2012-08-23 12:29 ` Yao Qi
2012-08-23 18:03 ` Pedro Alves
2012-08-24 13:38 ` Jan Kratochvil [this message]
2012-08-24 15:41 ` Pedro Alves
2012-08-24 16:19 ` Jan Kratochvil
2012-08-24 16:53 ` Pedro Alves
2012-08-24 16:57 ` Pedro Alves
2012-08-24 17:12 ` Jan Kratochvil
2012-08-27 10:33 ` Yao Qi
2012-08-27 13:07 ` Jan Kratochvil
2012-08-27 15:15 ` Yao Qi
2012-08-27 15:57 ` Jan Kratochvil
2012-08-24 13:34 ` [PATCH 1/2] Append "." in error message Jan Kratochvil
2012-08-24 13:40 ` RFC: consolidate checks for _Unwind_DebugHook in test suite Jan Kratochvil
2012-08-24 13:54 ` Tom Tromey
2012-08-24 14:08 ` Jan Kratochvil
2012-08-24 15:26 ` 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=20120824133738.GB5219@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@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