public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "marco.marsala at live dot it" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27144] New: Just attaching and detaching gdb crashes the Inferior
Date: Sun, 03 Jan 2021 18:41:30 +0000	[thread overview]
Message-ID: <bug-27144-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27144
           Summary: Just attaching and detaching gdb crashes the Inferior
           Product: gdb
           Version: 10.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: marco.marsala at live dot it
  Target Milestone: ---

With a specific executable (I could share that), attach gdb to that process:

gdb -p PID

then detach it, without doing anything else:

gdb) detach

crashes the process (PID, not gdb). Just before crashing, that process outputs:
“Unable to block on epool”

This happens only with a specific executable. Just attaching and detaching
should not cause that.

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

             reply	other threads:[~2021-01-03 18:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 18:41 marco.marsala at live dot it [this message]
2021-01-03 20:29 ` [Bug gdb/27144] " marco.marsala at live dot it
2021-01-04  0:14 ` simark at simark dot ca
2021-01-04 17:20 ` marco.marsala at live dot it
2021-01-04 17:54 ` simark at simark dot ca

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