public inbox for
help / color / mirror / Atom feed
From: "dbrumley at forallsecure dot com" <>
Subject: [Bug gdb/30847] gdbtypes.c:3355: internal-error causes gdb to abort when setting breakpoint
Date: Thu, 21 Sep 2023 14:51:18 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #5 from David Brumley <dbrumley at forallsecure dot com> ---

First, thank you for helping me understand the issue.  Your deep knowledge and
fast response times to something as weird as my bug report are much

I felt you might be interested in the lecture, and not sure that was useful for
the list.

Here are my slides, with the particular CVE starting on page 21:

* I'm a big believer in the growth mindset, so if you happen to look and see
something wrong, please let me know! It's how I get better!

* As you can see, I ended up building from source code anyway.

Editing the symbol table was pretty easy.  I've done it manually in the past,
but I found a very nice library called lief recently.

import lief
binary = lief.parse('extract75')
errno = next(filter(lambda e: ( ) == "errno",
stdin = next(filter(lambda e: ( ) == "stdin",
binary.symbols)) ( ) = ( )

Thanks again!

Best wishes,


Dr. David Brumley

Executive Assistant: Teressa Peirona < >

On Wed, Sep 20, 2023 at 7:07 PM, tromey at sourceware dot org < > wrote:

> https:/ / sourceware. org/ bugzilla/ show_bug. cgi?id=30847 (
> )
> --- Comment #4 from Tom Tromey <tromey at sourceware dot org> --- I
> totally misread that as you rebuilding your program -- but you rebuilt gdb
> (which you said...).
> Sorry about that. Anyway this bug is probably not hard to fix, and the
> backtrace is handy for diagnosing w/o sources. So, thank you.
> --
> You are receiving this mail because:
> You reported the bug.

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

  parent reply	other threads:[~2023-09-21 14:51 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 [this message]
2023-09-21 20:23 ` dbrumley at forallsecure dot com
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).