public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25723] AddressSanitizer: heap-buffer-overflow in fixup_section
Date: Wed, 25 Mar 2020 18:42:51 +0000 [thread overview]
Message-ID: <bug-25723-4717-GyKI3fis8I@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25723-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25723
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> [ Could be related to PR25479: "AddressSanitizer: heap-buffer-overflow in
> lookup_minimal_symbol_by_pc_name" . Also there there's fixup_section in the
> call stack. ]
>
Both gdb.base/readline-ask.exp and gdb.dwarf2/dw2-icc-opaque.exp bisect to
commit 6a053cb1ff6, same as PR25479.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-03-25 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 16:55 [Bug gdb/25723] New: " vries at gcc dot gnu.org
2020-03-25 17:04 ` [Bug gdb/25723] " vries at gcc dot gnu.org
2020-03-25 18:42 ` vries at gcc dot gnu.org [this message]
2020-03-25 18:43 ` vries at gcc dot gnu.org
2022-06-29 13:12 ` vries at gcc dot gnu.org
2022-06-30 11:20 ` vries at gcc dot gnu.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-25723-4717-GyKI3fis8I@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).