* [Bug gdb/29040] [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
2022-04-10 16:51 [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 vries at gcc dot gnu.org
@ 2022-04-10 16:52 ` vries at gcc dot gnu.org
2022-04-10 18:30 ` simark at simark dot ca
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: vries at gcc dot gnu.org @ 2022-04-10 16:52 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29040
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug gdb/29040] [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
2022-04-10 16:51 [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 vries at gcc dot gnu.org
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
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: simark at simark dot ca @ 2022-04-10 18:30 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29040
--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
I saw it on first try on Ubuntu 20.04, so it seems to reproduce reliably.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug gdb/29040] [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
2022-04-10 16:51 [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 vries at gcc dot gnu.org
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
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: vries at gcc dot gnu.org @ 2022-05-13 10:19 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29040
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Hmm, looks unrelated sofar, but this is wrong:
...
ret = waitpid (pid, &stat, 0);
} while (ret == EINTR);
...
and should be:
...
ret = waitpid (pid, &stat, 0);
} while (ret == -1 && errno == EINTR);
...
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug gdb/29040] [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
2022-04-10 16:51 [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 vries at gcc dot gnu.org
` (2 preceding siblings ...)
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
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: vries at gcc dot gnu.org @ 2022-05-13 10:47 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29040
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Hmm, so WIFEXITED is false, and WIFSIGNALED is true, with WTERMSIG == 11, which
is SIGSEGV.
Documentation of WIFEXITED:
...
WIFEXITED(wstatus)
returns true if the child terminated normally, that is, by calling exit(3) or
_exit(2), or by returning from main().
...
Curious is that we have "_exit (11)" in the test-case. But perhaps that's a
red herring.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug gdb/29040] [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
2022-04-10 16:51 [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 vries at gcc dot gnu.org
` (3 preceding siblings ...)
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
6 siblings, 0 replies; 8+ messages in thread
From: vries at gcc dot gnu.org @ 2022-05-13 13:12 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29040
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
I tried to catch the segfault using an install handler, which prints the pid
and then goes to sleep, such that I might attach to it. But doing so changes
the reported signal into a SIGTRAP.
So I'm out of idea atm.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug gdb/29040] [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
2022-04-10 16:51 [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 vries at gcc dot gnu.org
` (4 preceding siblings ...)
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
6 siblings, 0 replies; 8+ messages in thread
From: schwab@linux-m68k.org @ 2022-05-13 14:01 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29040
--- Comment #5 from Andreas Schwab <schwab@linux-m68k.org> ---
The child is jumping to NULL somewhere.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00000000 in ?? ()
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug gdb/29040] [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
2022-04-10 16:51 [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 vries at gcc dot gnu.org
` (5 preceding siblings ...)
2022-05-13 14:01 ` schwab@linux-m68k.org
@ 2022-10-02 18:19 ` vries at gcc dot gnu.org
6 siblings, 0 replies; 8+ messages in thread
From: vries at gcc dot gnu.org @ 2022-10-02 18:19 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29040
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)
> Hmm, looks unrelated sofar, but this is wrong:
> ...
> ret = waitpid (pid, &stat, 0);
> } while (ret == EINTR);
> ...
> and should be:
> ...
> ret = waitpid (pid, &stat, 0);
> } while (ret == -1 && errno == EINTR);
> ...
Fixed in
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=4cfa9edb35736ddf4efd2bd8ccc885349dc69b8e
.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread