public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dbrumley at forallsecure dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30847] gdbtypes.c:3355: internal-error causes gdb to abort when setting breakpoint
Date: Thu, 21 Sep 2023 20:23:44 +0000	[thread overview]
Message-ID: <bug-30847-4717-XGWGCuyaEc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30847-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30847

--- Comment #6 from David Brumley <dbrumley at forallsecure dot com> ---
I didn't answer the stab question; apologies.

I don't have a super strong opinion here. Older binaries are pretty prevalent
in cyber-physical systems (airplanes, power, etc) since the system deployment
timeline is often decades. It's always nice if the latest gdb just works, and I
think relevant to the sysadmin or security trying to diagnose issues.  Those
same people typically don't have source.

It's totally reasonable to deprioritize and just recommend they use an older
gdb. It's a question, at least to me, of how much the focus is on the developer
vs. users of compiled code.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-09-21 20:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14  0:55 [Bug gdb/30847] New: " dbrumley at forallsecure dot com
2023-09-14 12:51 ` [Bug gdb/30847] " tromey at sourceware dot org
2023-09-20 14:42 ` dbrumley at forallsecure dot com
2023-09-20 19:16 ` tromey at sourceware dot org
2023-09-20 23:07 ` tromey at sourceware dot org
2023-09-21 14:51 ` dbrumley at forallsecure dot com
2023-09-21 20:23 ` dbrumley at forallsecure dot com [this message]
2024-02-09 18:56 ` 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-30847-4717-XGWGCuyaEc@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).