From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3F0153858D32; Sat, 10 Feb 2024 10:26:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3F0153858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1707560786; bh=mZRMnn2vESPhf+oTDEuMm7bmwHAn8QWwwksoRKGQE18=; h=From:To:Subject:Date:In-Reply-To:References:From; b=EVpY+nMankSakaCxP2KRZ8UAmtauIHR0jxq/ACjEjAnCHjo1hN1+l1Ph+sLF2o6lc a9UX6w2whINXIXJQgIznktn1WhCzundxeycKhtXrWtIbZuO6EK9yyH7HYqweOtVHQZ n6HpC/i/gYltNfAAtw+Z5VGS+WjC4answsS8VY+Y= From: "korcankaraokcu at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/31359] Unable to stop proton or wine games after a breakpoint gets triggered Date: Sat, 10 Feb 2024 10:26:25 +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: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: korcankaraokcu at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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=3D31359 --- Comment #2 from Korcan Karaok=C3=A7u = --- (In reply to Tom Tromey from comment #1) > You're sending "interrupt"? (BTW there's an MI command, "-exec-interrupt= ") >=20 > That probably won't work unless you've also requested MI > async mode, like "-gdb-set mi-async on". Is your program > doing this? I know the mi counterpart for interrupt exists, it's just that the code is = old and since it works, I haven't changed it I've tried executing "-gdb-set mi-async on" before attaching and the result= is the same. I've also tested with regular gdb, without mi interpreter, outcom= e is still the same Btw, the more I tested, the more I've seen the other outcomes. In most of my tests, the application crashed after the step 5 at the first try. I'm curre= ntly testing on small games, Moonring on steam (proton) and Minesweeper on wine. Moonring is free, test it for yourself if you want. Sometimes they just wor= k as usual, but mostly they just crash after step 5. I'll be changing the title = to reflect the other outcomes, such as crash --=20 You are receiving this mail because: You are on the CC list for the bug.=