public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25479] AddressSanitizer: heap-buffer-overflow in lookup_minimal_symbol_by_pc_name
Date: Thu, 26 Mar 2020 02:06:41 +0000 [thread overview]
Message-ID: <bug-25479-4717-uJ7TfbpRtM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25479-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25479
--- Comment #8 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Christian Biesinger from comment #7)
> (In reply to Tom Tromey from comment #5)
> > I've looked at it a little. I tend to think it is a pre-existing
> > bug. I suspect Address Sanitizer doesn't understand how to examine
> > objects allocated on an obstack (neither does valgrind...), which is
> > why this was never detected.
>
> Offtopic, but Valgrind can be taught this:
> http://valgrind.org/docs/manual/mc-manual.html#mc-manual.mempools
> I've been meaning to look into that.
Yeah, me too. We also use a similar thing, "objalloc", via BFD
(obstack was deemed too heavy, lol, by someone in ancient times).
I imagine marking that up would reveal all the lurking BFD bugs.
--
You are receiving this mail because:
You are on the CC list for the bug.
next parent reply other threads:[~2020-03-26 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25479-4717@http.sourceware.org/bugzilla/>
2020-03-26 2:06 ` tromey at sourceware dot org [this message]
2023-02-12 2:56 ` sam at gentoo dot org
2023-03-05 17:35 ` tromey at sourceware dot org
2023-03-05 17:39 ` 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-25479-4717-uJ7TfbpRtM@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).