From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BE5BE3858D38; Fri, 12 Apr 2024 08:50:37 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BE5BE3858D38 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1712911837; bh=obaYUYlbQiPikbEQSeOzl3I9XTu+nOKd2f3fwfpzBNI=; h=From:To:Subject:Date:From; b=ICrA61BVLFKvse7WXz/tGj5XEZof3U8kKxRaoXPV0uwMcqvXAWOWEMVFqGZCtn77S karjdURiUFlWvT1DhDdH63u1mIfdTiVcGlDcmdvnq0NFPijYycTTsGCmaiU1etReOw 4ewNeSuvd+KQQu+BCCC7w5OEWxufvAlmFUj3Nk34= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/31633] New: [gdb/testsuite] FAIL: gdb.server/server-kill-python.exp: ensure inferior is running Date: Fri, 12 Apr 2024 08:50:36 +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: 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31633 Bug ID: 31633 Summary: [gdb/testsuite] FAIL: gdb.server/server-kill-python.exp: ensure inferior is running 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 looking into PR31632, I did the following experiment. In the sources: ... $ cd gdb/testsuite $ mkdir backup $ mv gdb.*/backup $ mv backup/gdb.server backup/gdb.xml . ... In the build dir: ... $ make -j 16 \ check//unix/-m64 \ check//unix/-m64/-fPIE/-pie\ check//unix/-m32 \ check//unix/-m32/-fPIE/-pie ... I reproducibly run into a FAIL in gdb.server/server-kill-python: ... $ grep ^FAIL: build/gdb/testsuite.*/gdb.sum build/gdb/testsuite.unix.-m32.-fPIE.-pie/gdb.sum:FAIL: gdb.server/server-kill-python.exp: ensure inferior is running build/gdb/testsuite.unix.-m32/gdb.sum:FAIL: gdb.server/server-kill-python.e= xp: ensure inferior is running ... In more detail: ... spawn /data/vries/gdb/leap-15-5/build/gdb/testsuite.unix.-m32/../../gdb/gdbserver= /gdbserver --once localhost:2346 /data/vries/gdb/leap-15-5/build/gdb/testsuite.unix.-m32/outputs/gdb.server/= server-kill-python/server-kill-python^M Process /data/vries/gdb/leap-15-5/build/gdb/testsuite.unix.-m32/outputs/gdb.server/= server-kill-python/server-kill-python created; pid =3D 3817^M Listening on port 2346^M spawn /data/vries/gdb/leap-15-5/build/gdb/testsuite.unix.-m32/../../gdb/gdb= -nw -nx -data-directory /data/vries/gdb/leap-15-5/build/gdb/testsuite.unix.-m32/../data-directory -quiet -iex set height 0 -iex set width 0 -ex source /data/vries/gdb/leap-15-5/build/gdb/testsuite.unix.-m32/outputs/gdb.server/= server-kill-python/file1.py^M Remote debugging from host ::1, port 38736^M FAIL: gdb.server/server-kill-python.exp: ensure inferior is running ... I.m able to reproduce this with plain target board unix/-m32 at the origina= ting commit. --=20 You are receiving this mail because: You are on the CC list for the bug.=