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 gdb/31066] New: [gdb] FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: detach: watchpoint:hw: detach parent (timeout)
Date: Tue, 14 Nov 2023 07:59:05 +0000	[thread overview]
Message-ID: <bug-31066-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31066
           Summary: [gdb] FAIL:
                    gdb.threads/process-dies-while-detaching.exp:
                    multi-process: detach: watchpoint:hw: detach parent
                    (timeout)
           Product: gdb
           Version: 13.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

On SLE-11 with a gdb 13.2 based package I ran into:
...
(gdb) PASS: gdb.threads/process-dies-while-detaching.exp: multi-process:
detach: watchpoint:hw: switch to parent
detach^M
Detaching from program:
/usr/src/packages/BUILD/gdb-13.2/build-x86_64-suse-linux/gdb/testsuite.unix.-m64.-fPIE.-pie/outputs/gdb.threads/process-dies-while-detaching/process-dies-while-detaching-1-detach,
process 18659^M
[Inferior 1 (process 18659) detached]^M
signaled, sig=15^M
(gdb) saw prompt
FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: detach:
watchpoint:hw: detach parent (timeout)
...

15 means SIGTERM.

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

                 reply	other threads:[~2023-11-14  7:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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