From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 105415 invoked by alias); 12 Mar 2015 12:59:42 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 104341 invoked by uid 48); 12 Mar 2015 12:59:41 -0000 From: "palves at redhat dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-q1/txt/msg00428.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=17760 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves --- "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.