public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.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	[thread overview]
Message-ID: <bug-31633-4717@http.sourceware.org/bugzilla/> (raw)

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

            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.exp:
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 = 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 originating
commit.

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

             reply	other threads:[~2024-04-12  8:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12  8:50 vries at gcc dot gnu.org [this message]
2024-04-12  9:14 ` [Bug testsuite/31633] " vries at gcc dot gnu.org
2024-04-12 17:51 ` vries at gcc dot gnu.org
2024-04-17  9:44 ` cvs-commit at gcc dot gnu.org
2024-04-17  9:46 ` vries at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-31633-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).