[Bug tdep/31016] New: [gdb/tdep, ppc64le] FAIL: gdb.mi/mi-condbreak-throw.exp: unwind_on_exception=off: wait for stop (timeout)

[Bug tdep/31016] New: [gdb/tdep, ppc64le] FAIL: gdb.mi/mi-condbreak-throw.exp: unwind_on_exception=off: wait for stop (timeout)

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=31016

            Bug ID: 31016
           Summary: [gdb/tdep, ppc64le] FAIL:
                    gdb.mi/mi-condbreak-throw.exp:
                    unwind_on_exception=off: wait for stop (timeout)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

With gdb-14-branch on CentOS-7 ppc64le power9 (cfarm135), I get:
...
PASS: gdb.mi/mi-condbreak-throw.exp: unwind_on_exception=off: get number for
breakpoint
-exec-continue^M
^running^M
*running,thread-id="all"^M
(gdb) ^M
Expecting: ^([^M
]+)?(.*~"\\nProgram"^M
~" received signal SIGABRT, Aborted\.\\n"(?:^M
[~&]"[^^M
]+")*^M
\*stopped,reason="signal-received",signal-name="SIGABRT"[^^M
]+frame=\{addr="0x[0-9A-Fa-f]+",[^^M
]+\}[^^M
]+^M
&"Error in testing condition for breakpoint 2:\\n"^M
&"The program being debugged was signaled while in a function called from
GDB\.\\n"^M
&"GDB remains in the frame where the signal was received\.\\n"^M
&"To change this behavior use \\"set unwindonsignal on\\"\.\\n"^M
&"Evaluation of the expression containing the function\\n"^M
&"\(cond_throw\(\)\) will be abandoned\.\\n"^M
&"When the function is done executing, GDB will silently stop\.\\n"^M
=breakpoint-modified,bkpt={number="2",type="breakpoint",[^^M
]+times="1",[^^M
]+}[^M
]+[(]gdb[)] ^M
[ ]*)
FAIL: gdb.mi/mi-condbreak-throw.exp: unwind_on_exception=off: wait for stop
(timeout)
...

Reproduces with a simple:
...
$ gdb -q \
    outputs/gdb.mi/mi-condbreak-throw/mi-condbreak-throw \
    -ex start \
    -ex "call cond_throw ()"
Reading symbols from
build/gdb/testsuite/outputs/gdb.mi/mi-condbreak-throw/mi-condbreak-throw...
Temporary breakpoint 1 at 0x1000089c: file
/home/vries/gdb/src/gdb/testsuite/gdb.mi/mi-condbreak-throw.cc, line 36.
Starting program:
/home/vries/gdb/build/gdb/testsuite/outputs/gdb.mi/mi-condbreak-throw/mi-condbreak-throw 

Temporary breakpoint 1, main () at
/home/vries/gdb/src/gdb/testsuite/gdb.mi/mi-condbreak-throw.cc:36
36        int res = foo ();
< ... hangs ... >
^C
Program received signal SIGINT, Interrupt.
0x00007ffff7ccaf04 in ?? () from /lib64/libgcc_s.so.1
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on".
Evaluation of the expression containing the function
(cond_throw()) will be abandoned.
When the function is done executing, GDB will silently stop.
(gdb) bt
#0  0x00007ffff7ccaf04 in ?? () from /lib64/libgcc_s.so.1
#1  0x00007ffff7ccc9b0 in _Unwind_RaiseException () from /lib64/libgcc_s.so.1
#2  0x00007ffff7e7ba94 in __cxa_throw () from /lib64/libstdc++.so.6
#3  0x0000000010000818 in cond_throw () at
/home/vries/gdb/src/gdb/testsuite/gdb.mi/mi-condbreak-throw.cc:23
#4  <function called from gdb>
#5  main () at
/home/vries/gdb/src/gdb/testsuite/gdb.mi/mi-condbreak-throw.cc:36
(gdb) 
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug tdep/31016] [gdb/tdep, ppc64le] FAIL: gdb.mi/mi-condbreak-throw.exp: unwind_on_exception=off: wait for stop (timeout)

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=31016

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Hmm, this looks like a dup of PR30549.

-- 
You are receiving this mail because:
You are on the CC list for the bug.