From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9E1CA3858C33; Fri, 22 Mar 2024 16:43:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9E1CA3858C33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1711125814; bh=LqY8nz3JkmkQI5Lcng0uV7fW+KpZwd72c/043OxZb0Y=; h=From:To:Subject:Date:In-Reply-To:References:From; b=asBMRFHf3iNXDkmQHtAwJ3pHmVsaJ4dW3kR7ZCZvtPT4FIf3YKvTY+0EUFNp1EL0C VQ0m6ETsfozrmg+likANCBjWXEAgo06evsdL0ZWA7LDg1+ama9cpTQeaWN1+to8aJM 2jxGGg3LX7kTuOTdUsgNTOGd46oQp/fQClL29mfs= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/31524] Can't start program in Lazarus/fpc with activated debugging Date: Fri, 22 Mar 2024 16:43:33 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 13.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: WAITING 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: cc everconfirmed cf_reconfirmed_on 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=3D31524 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg Ever confirmed|0 |1 Last reconfirmed| |2024-03-22 Status|UNCONFIRMED |WAITING --- Comment #1 from Tom Tromey --- (In reply to Reinhard Buchholz from comment #0) Hi. Thank you for the bug report. > gdb encountered an internal error: Press "OK" to continue debugging. This > may not be safe. Press "Stop" to end the debugging session. Unfortunately this isn't enough information to know what's gone wrong. Could you possibly get a trace of the MI commands sent to gdb, and the full output from gdb? Maybe that would help. It might at least show where the internal error occurs. --=20 You are receiving this mail because: You are on the CC list for the bug.=