public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30764] SUMMARY: AddressSanitizer: heap-use-after-free /home/root/gdb/binutils-gdb-gdb-13.1-release/gdb/coff-pe-read.c:137 in add_pe_exported_sym Date: Tue, 15 Aug 2023 16:37:59 +0000 [thread overview] Message-ID: <bug-30764-4717-HmR2wErq0t@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30764-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30764 Keith Seitz <keiths at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #1 from Keith Seitz <keiths at redhat dot com> --- Like 30763, I can reproduce this on gdb-13-branch. Also like the earlier bug, origin/master does NOT reproduce this. The same commit (2db20b97f1dc3e5dce3d6ed74a8a62f0dede8c80) fixes this, too. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-15 16:37 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-15 7:15 [Bug gdb/30764] New: " sihan2021 at iscas dot ac.cn 2023-08-15 16:37 ` keiths at redhat dot com [this message] 2023-08-16 12:25 ` [Bug gdb/30764] " 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-30764-4717-HmR2wErq0t@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: linkBe 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).