public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "reinhard.buchholz at arcor dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31524] New: Can't start program in Lazarus/fpc with activated debugging
Date: Thu, 21 Mar 2024 20:12:20 +0000 [thread overview]
Message-ID: <bug-31524-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31524
Bug ID: 31524
Summary: Can't start program in Lazarus/fpc with activated
debugging
Product: gdb
Version: 13.1
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: reinhard.buchholz at arcor dot de
Target Milestone: ---
After automatic update in Linux SUSE Enterprise 15 from
gdb 12.1-150400.15.9.1-xf86_64 to 13.2-150400.15.14.1-xf86_64
my program stops with the message
gdb encountered an internal error: Press "OK" to continue debugging. This may
not be safe. Press "Stop" to end the debugging session.
If I press "Continue" I get the message
While executing the command:
"TGDBMIDebuggerInstruction: "ptype Shortstring", [ifRequiresMemLimit]"
gdb reported:
"&"A fatal error internal to GDB has been detected, further\ndebugging is not
possible. GDB will now terminate.\n\n"
&"This is a bug, please report it.""
The I get the message
Debuggerfehler
Der Debugger ist abgestürzt mit Status
Speichern Sie Ihre Arbeit jetzt!
Drücken Sie "Stop" und hoffen auf einen Fix für diesen Fehler.
The gdb process is no longer running.
gdb -v reports Version 13.2, but I this version-number in not choosable.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2024-03-21 20:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 20:12 reinhard.buchholz at arcor dot de [this message]
2024-03-22 16:43 ` [Bug gdb/31524] " tromey at sourceware dot org
2024-03-22 19:28 ` reinhard.buchholz at arcor dot de
2024-03-24 21:17 ` tromey at sourceware dot org
2024-03-25 19:48 ` reinhard.buchholz at arcor dot de
2024-03-25 20:05 ` reinhard.buchholz at arcor dot de
2024-03-25 20:19 ` reinhard.buchholz at arcor dot de
2024-03-25 22:41 ` tromey at sourceware dot org
2024-03-26 13:29 ` reinhard.buchholz at arcor dot de
2024-03-27 1:19 ` tromey at sourceware dot org
2024-03-27 3:40 ` tromey at sourceware dot org
2024-03-27 12:51 ` reinhard.buchholz at arcor dot de
2024-03-27 13:43 ` tromey at sourceware dot org
2024-03-27 16:42 ` tromey at sourceware dot org
2024-03-28 22:31 ` cvs-commit at gcc dot gnu.org
2024-03-28 22:32 ` tromey at sourceware dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-31524-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).