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/30640] AddressSanitizer: heap-use-after-free /home/root/sp/Dataset/Binutils/binutils_aflpp/gdb/coff-pe-read.c:137:27
Date: Wed, 26 Jul 2023 19:44:36 +0000 [thread overview]
Message-ID: <bug-30640-4717-zuTvrvqb1q@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30640-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30640
Keith Seitz <keiths at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |keiths at redhat dot com
--- Comment #2 from Keith Seitz <keiths at redhat dot com> ---
Can you confirm the location on origin/master with the provided binary?
The provided backtrace does not appear to be the same, i.e.,
add_pe_exported_sym
does not appear at all in my backtrace:
$ ./gdb -nx -q --data-directory data-directory UAF_2
Reading symbols from UAF_2...
Fatal signal: Segmentation fault
----- Backtrace -----
0x599064 gdb_internal_backtrace_1
../../src/gdb/bt-utils.c:122
0x599107 _Z22gdb_internal_backtracev
../../src/gdb/bt-utils.c:168
0x782fd4 handle_fatal_signal
../../src/gdb/event-top.c:889
0x783140 handle_sigsegv
../../src/gdb/event-top.c:962
0x7f0dc145fb6f ???
0x7f0dc1581c11 ???
0x60b27a read_pe_truncate_name
../../src/gdb/coff-pe-read.c:249
0x60c019 _Z21read_pe_exported_symsR21minimal_symbol_readerP7objfile
../../src/gdb/coff-pe-read.c:498
0x60e0bb coff_read_minsyms
../../src/gdb/coffread.c:543
0x60e629 coff_symfile_read
../../src/gdb/coffread.c:698
0xbd975e read_symbols
../../src/gdb/symfile.c:772
0xbd9e0b syms_from_objfile_1
../../src/gdb/symfile.c:966
0xbd9ecf syms_from_objfile
../../src/gdb/symfile.c:983
0xbda3aa symbol_file_add_with_addrs
../../src/gdb/symfile.c:1086
0xbda6eb
_Z24symbol_file_add_from_bfdRKN3gdb7ref_ptrI3bfd18gdb_bfd_ref_policyEEPKc10enum_flagsI16symfile_add_flagEPSt6vectorI14other_sectionsSaISC_EES8_I12objfile_flagEP7objfile
../../src/gdb/symfile.c:1166
0xbda73a
_Z15symbol_file_addPKc10enum_flagsI16symfile_add_flagEPSt6vectorI14other_sectionsSaIS5_EES1_I12objfile_flagE
../../src/gdb/symfile.c:1179
0xbda7ff symbol_file_add_main_1
../../src/gdb/symfile.c:1203
0xbda7a6 _Z20symbol_file_add_mainPKc10enum_flagsI16symfile_add_flagE
../../src/gdb/symfile.c:1194
0x90b1d7 symbol_file_add_main_adapter
../../src/gdb/main.c:549
0x90b0ed catch_command_errors
../../src/gdb/main.c:518
0x90c20e captured_main_1
../../src/gdb/main.c:1203
0x90c820 captured_main
../../src/gdb/main.c:1310
0x90c8bf _Z8gdb_mainP18captured_main_args
../../src/gdb/main.c:1339
0x418c3c main
../../src/gdb/gdb.c:32
---------------------
A fatal error internal to GDB has been detected, further
debugging is not possible. GDB will now terminate.
This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.
Segmentation fault (core dumped)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-26 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 6:32 [Bug gdb/30640] New: " sihan2021 at iscas dot ac.cn
2023-07-15 6:32 ` [Bug gdb/30640] " sihan2021 at iscas dot ac.cn
2023-07-26 19:44 ` keiths at redhat dot com [this message]
2023-07-29 5:42 ` sihan2021 at iscas dot ac.cn
2023-07-29 5:43 ` sihan2021 at iscas dot ac.cn
2023-07-29 5:44 ` sihan2021 at iscas dot ac.cn
2023-07-29 6:07 ` sihan2021 at iscas dot ac.cn
2023-09-28 14:47 ` keiths at redhat dot com
2023-09-28 19:07 ` keiths at redhat dot com
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-30640-4717-zuTvrvqb1q@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).