[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

[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]

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.

[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

[vries at gcc dot gnu.org]

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.

[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

[simark at simark dot ca]

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.

[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

[vries at gcc dot gnu.org]

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.

[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

[vries at gcc dot gnu.org]

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.

[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

[vries at gcc dot gnu.org]

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.

[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

[schwab@linux-m68k.org]

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.

[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

[vries at gcc dot gnu.org]

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.