public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/11503] Cannot attach to lwp
Date: Tue, 29 Nov 2022 19:05:56 +0000	[thread overview]
Message-ID: <bug-11503-4717-zk43l1Aahf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11503-4717@http.sourceware.org/bugzilla/>

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
                 CC|                            |tromey at sourceware dot org
   Last reconfirmed|                            |2022-11-29
             Status|UNCONFIRMED                 |WAITING

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
Is this bug still relevant to you?

> gdbserver: Could not attach 

This may mean some config issue on your system, like either
permissions (running the program and gdbserver as different users)
or some security feature disabling ptrace.

> Cannot find new threads: debugger service failed

This also seems pretty bad.

I wonder if the uclib+nptl combo is the issue.

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

       reply	other threads:[~2022-11-29 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11503-4717@http.sourceware.org/bugzilla/>
2022-11-29 19:05 ` tromey at sourceware dot org [this message]
2010-04-16  4:37 [Bug gdb/11503] New: " sreekumar dot tp at gmail dot com
2010-04-16  4:37 ` [Bug gdb/11503] " sreekumar dot tp at gmail dot com

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-11503-4717-zk43l1Aahf@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).