From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 72F48385E838; Wed, 10 Jan 2024 18:33:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 72F48385E838 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1704911603; bh=bmEA6VQ1c0XgqDH0oYXbCMKP+kB6lDY9hY5FcN1aKB0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=BC1JOMCvadVLNEnDypH9D8PwyYX3lJ36E8ISFXpjt1DVSu/c9jTAqJZGCkzIehQSG tNRnf1i2QlT4V6qL9MQbtOCCHuR+8t9IIzN7TLc5odKYQ50RU4l5PbFKjL5eqjyGFt aCMbjGmQUuUUHaz3b72m6L/UdWb+Y3m0/vipKki8= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/9834] GDB choosing wrong process when multiple processes have same name. Date: Wed, 10 Jan 2024 18:33:22 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 6.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: OBSOLETE X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 6.8 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution cc bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D9834 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |OBSOLETE CC| |tromey at sourceware dot o= rg Status|UNCONFIRMED |RESOLVED --- Comment #4 from Tom Tromey --- I think for very old bug reports like this, without a solid reproducer, we can normally just close them. In this case, Windows attach is reasonably well-tested nowadays; e.g. AdaCore tests it daily. So whatever this was, it is probably fixed. --=20 You are receiving this mail because: You are on the CC list for the bug.=