[Bug testsuite/29025] [gdb/testsuite] FAIL: gdb.mi/mi-cmd-user-context.exp: frame {1,2,3} (unexpected output)

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> While running the gdb testsuite for gdb-12-branch on openSUSE Tumbleweed, I
> ran into:
> ...
> FAIL: gdb.mi/mi-cmd-user-context.exp: frame 1 (unexpected output)
> FAIL: gdb.mi/mi-cmd-user-context.exp: frame 2 (unexpected output)
> FAIL: gdb.mi/mi-cmd-user-context.exp: frame 3 (unexpected output)
> ...
> 

Hm, actually the original FAIL was a reproduction of the problem fixed by this
( https://sourceware.org/pipermail/gdb-patches/2022-April/187319.html ):
...
PASS: gdb.mi/mi-cmd-user-context.exp: info thread 5
Expecting: ^(frame[^M
]+)?(.*#0  0x.*[^M
]+[(]gdb[)] ^M
[ ]*)
frame^M
&"frame\n"^M
~"#0  child_sub_function () at
/data/vries/gdb_versions/devel/src/gdb/testsuite/gdb.mi/u\
ser-selected-context-sync.c:33\n"^M
~"33\t    dummy = !dummy; /* thread loop line */\n"^M
^done^M
(gdb) ^M
FAIL: gdb.mi/mi-cmd-user-context.exp: frame 1 (unexpected output)
...

The detailed FAIL listed in comment 0, is what I got when trying reproduce.

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