From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Simon Marchi <simark@simark.ca>
Subject: [PATCH] Fix skip.exp test failure observed with gcc-9.2.0
Date: Sun, 15 Dec 2019 11:30:00 -0000 [thread overview]
Message-ID: <AM0PR08MB3714C86181FA179F9BA0266AE4560@AM0PR08MB3714.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <AM0PR08MB3714A919F6C50D7EEB19C302E4560@AM0PR08MB3714.eurprd08.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
Hi,
this is the split out patch on skip.exp which fixes a pre-existing
compatibilty issue with that test case and gcc-9.2.0 (and gcc-10 from
trunk of a few weeks ago at least, likely other versions too).
Is it OK for trunk?
Thanks
Bernd.
[-- Attachment #2: changelog.txt --]
[-- Type: text/plain, Size: 136 bytes --]
gdb/testsuite:
2019-12-15 Bernd Edlinger <bernd.edlinger@hotmail.de>
* gdb.base/skip.exp: Fix test failure observed with gcc-9.2.0.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0001-Fix-skip.exp-test-failure-observed-with-gcc-9.2.0.patch --]
[-- Type: text/x-patch; name="0001-Fix-skip.exp-test-failure-observed-with-gcc-9.2.0.patch", Size: 2595 bytes --]
From b15964b769373f25f276430914c5efa84d411032 Mon Sep 17 00:00:00 2001
From: Bernd Edlinger <bernd.edlinger@hotmail.de>
Date: Sun, 15 Dec 2019 11:05:47 +0100
Subject: [PATCH] Fix skip.exp test failure observed with gcc-9.2.0
Need to step a second time because with this gcc version
the first step jumps back to main before entering foo.
---
gdb/testsuite/gdb.base/skip.exp | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/gdb/testsuite/gdb.base/skip.exp b/gdb/testsuite/gdb.base/skip.exp
index d763194..15dec42 100644
--- a/gdb/testsuite/gdb.base/skip.exp
+++ b/gdb/testsuite/gdb.base/skip.exp
@@ -21,8 +21,8 @@ load_lib completion-support.exp
standard_testfile
if { [prepare_for_testing "failed to prepare" "skip" \
- {skip.c skip1.c } \
- {debug nowarnings}] } {
+ {skip.c skip1.c } \
+ {debug nowarnings}] } {
return -1
}
@@ -142,7 +142,9 @@ with_test_prefix "step after disabling 3" {
gdb_test "step" "bar \\(\\) at.*" "step 1"
gdb_test "step" ".*" "step 2"; # Return from foo()
- gdb_test "step" "foo \\(\\) at.*" "step 3"
+ # With gcc 9.2.0 we jump once back to main before entering foo here.
+ # If that happens try to step a second time.
+ gdb_test "step" "foo \\(\\) at.*" "step 3" "main \\(\\) at .*" "step"
gdb_test "step" ".*" "step 4"; # Return from bar()
gdb_test "step" "main \\(\\) at.*" "step 5"
}
@@ -261,7 +263,9 @@ with_test_prefix "step using -fu for baz" {
gdb_test_no_output "skip enable 7"
gdb_test "step" "bar \\(\\) at.*" "step 1"
gdb_test "step" ".*" "step 2"; # Return from bar()
- gdb_test "step" "foo \\(\\) at.*" "step 3"
+ # With gcc 9.2.0 we jump once back to main before entering foo here.
+ # If that happens try to step a second time.
+ gdb_test "step" "foo \\(\\) at.*" "step 3" "main \\(\\) at.*" "step"
gdb_test "step" ".*" "step 4"; # Return from foo()
gdb_test "step" "main \\(\\) at.*" "step 5"
}
@@ -276,7 +280,9 @@ with_test_prefix "step using -rfu for baz" {
gdb_test_no_output "skip enable 8"
gdb_test "step" "bar \\(\\) at.*" "step 1"
gdb_test "step" ".*" "step 2"; # Return from bar()
- gdb_test "step" "foo \\(\\) at.*" "step 3"
+ # With gcc 9.2.0 we jump once back to main before entering foo here.
+ # If that happens try to step a second time.
+ gdb_test "step" "foo \\(\\) at.*" "step 3" "main \\(\\) at.*" "step"
gdb_test "step" ".*" "step 4"; # Return from foo()
gdb_test "step" "main \\(\\) at.*" "step 5"
}
--
1.9.1
next parent reply other threads:[~2019-12-15 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM0PR08MB3714A919F6C50D7EEB19C302E4560@AM0PR08MB3714.eurprd08.prod.outlook.com>
2019-12-15 11:30 ` Bernd Edlinger [this message]
2019-12-15 13:05 ` Simon Marchi
2019-12-15 18:12 ` Bernd Edlinger
2019-12-17 2:44 ` Simon Marchi
2019-12-17 14:56 ` [PATCHv2] " Bernd Edlinger
2019-12-17 16:12 ` Simon Marchi
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=AM0PR08MB3714C86181FA179F9BA0266AE4560@AM0PR08MB3714.eurprd08.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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