This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug server/17760] gdbserver (MinGW) reports incorrect pid for a process being debugged
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 12 Mar 2015 12:59:40 +0000
- Subject: [Bug server/17760] gdbserver (MinGW) reports incorrect pid for a process being debugged
- Auto-submitted: auto-generated
- References: <bug-17760-4717 at http dot sourceware dot 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.