public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/17760] gdbserver (MinGW) reports incorrect pid for a process being debugged
Date: Thu, 12 Mar 2015 13:00:00 -0000 [thread overview]
Message-ID: <bug-17760-4717-r0alwD5sYX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17760-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17760
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
"42000" is a magic internal PID number that GDB uses whenever it can't figure
out the target's pid.
On GNU/Linux, GDBserver activates the multi-process extensions
(target_supports_multi_process) and thus GDB knows the real inferior's PID.
The trouble is that gdbserver's Windows backend doesn't support multi-process,
and so gdbserver doesn't tell GDB the real PID of the process.
Maybe we could activate the extensions even if the target backend can't debug
more than one process at a time. We'd need to make server.c refuse vRun /
vAttach if already debugging a process, on !target_supports_multi_process
targets, but it would probably works.
(tbc, not going to do it myself)
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2015-03-12 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 14:50 [Bug server/17760] New: " nikolay.koldunov at oracle dot com
2015-03-12 13:00 ` palves at redhat dot com [this message]
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-17760-4717-r0alwD5sYX@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).