From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 976883858009; Mon,  4 Apr 2022 14:13:37 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 976883858009
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29025] New: [gdb/testsuite] FAIL:
 gdb.mi/mi-cmd-user-context.exp: frame {1,2,3} (unexpected output)
Date: Mon, 04 Apr 2022 14:13:37 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-29025-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Apr 2022 14:13:37 -0000

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

            Bug ID: 29025
           Summary: [gdb/testsuite] FAIL: gdb.mi/mi-cmd-user-context.exp:
                    frame {1,2,3} (unexpected output)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

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)
...

I tried to reproduce, and managed by running in parallel with "stress -c 5"=
, 4
times in a run of 25.

The first FAIL looks like this in more detail:
...
PASS: gdb.mi/mi-cmd-user-context.exp: info thread 5
Expecting: ^(frame[^M
]+)?(.*#0  .*child_sub_function .*[^M
]+[(]gdb[)] ^M
[ ]*)
frame^M
&"frame\n"^M
~"#0  0x00007ffff7d3049a in pthread_barrier_wait@GLIBC_2.2.5 () from
/lib64/libc.so.6\n"\
^M
^done^M
(gdb) ^M
FAIL: gdb.mi/mi-cmd-user-context.exp: frame 1 (unexpected output)
...

Reading through the source code, the behaviour makes sense.

A breakpoint is set in main, after the call to pthread_barrier_wait.

This guarantees that when the breakpoint is hit, all threads have reached t=
he
barrier, and guarantees that the main thread has left the barrier, but not =
that
the other threads have left the barrier.=20

So at first glance this looks like a testsuite problem.

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