public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29040] New: [gdb/testsuite][m32] FAIL: gdb.threads/next-fork-other-thread.exp: fork_func=fork: target-non-stop=off: non-stop=off: displaced-stepping=on: i=8: next to other line
Date: Sun, 10 Apr 2022 16:51:56 +0000 [thread overview]
Message-ID: <bug-29040-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29040
Bug ID: 29040
Summary: [gdb/testsuite][m32] FAIL:
gdb.threads/next-fork-other-thread.exp:
fork_func=fork: target-non-stop=off: non-stop=off:
displaced-stepping=on: i=8: next to other line
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
When using target board unix/-m32, I run into:
...
(gdb) PASS: gdb.threads/next-fork-other-thread.exp: fork_func=fork:
target-non-stop=off: non-stop=off: displaced-stepping=on: i=7: next to break
here
next^M
next-fork-other-thread-fork:
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.threads/next-fork-other-thread.c:50:
forker: Assertion `WIFEXITED (stat)' failed.^M
^M
Thread 4 "next-fork-other" received signal SIGABRT, Aborted.^M
[Switching to Thread 0xf6c8cb40 (LWP 19912)]^M
0xf7fd2149 in __kernel_vsyscall ()^M
(gdb) FAIL: gdb.threads/next-fork-other-thread.exp: fork_func=fork:
target-non-stop=off: non-stop=off: displaced-stepping=on: i=8: next to other
line
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-04-10 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 16:51 vries at gcc dot gnu.org [this message]
2022-04-10 16:52 ` [Bug gdb/29040] " vries at gcc dot gnu.org
2022-04-10 18:30 ` simark at simark dot ca
2022-05-13 10:19 ` vries at gcc dot gnu.org
2022-05-13 10:47 ` vries at gcc dot gnu.org
2022-05-13 13:12 ` vries at gcc dot gnu.org
2022-05-13 14:01 ` schwab@linux-m68k.org
2022-10-02 18:19 ` vries at gcc dot gnu.org
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=bug-29040-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).