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 symtab/30707] New: [gdb/symtab] corrupted double-linked list in gdb.base/index-cache.exp Date: Mon, 31 Jul 2023 16:36:23 +0000 [thread overview] Message-ID: <bug-30707-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30707 Bug ID: 30707 Summary: [gdb/symtab] corrupted double-linked list in gdb.base/index-cache.exp Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- I build gdb on i686-linux native and ran the test-suite, and ran into: ... (gdb) file /home/netbook/gdb/build/gdb/testsuite/outputs/gdb.base/index-cache/index-cache^M Reading symbols from /home/netbook/gdb/build/gdb/testsuite/outputs/gdb.base/index-cache/index-cache...^M *** Error in `/home/netbook/gdb/build/gdb/testsuite/../../gdb/gdb': corrupted double-linked list: 0x09ec24d0 ***^M ^M ^M Fatal signal: Aborted^M ----- Backtrace -----^M 0x819f226 gdb_internal_backtrace_1^M /home/netbook/gdb/src/gdb/bt-utils.c:122^M 0x819f226 _Z22gdb_internal_backtracev^M /home/netbook/gdb/src/gdb/bt-utils.c:168^M 0x82d9dad handle_fatal_signal^M /home/netbook/gdb/src/gdb/event-top.c:889^M 0x400b4403 ???^M 0x400b4428 ???^M 0x40799686 ???^M 0x4079cab2 ???^M 0x407d3fd2 ???^M 0x407de4c9 ???^M 0x407e0943 ???^M 0x407e19d7 ???^M 0x407ceeab ???^M 0x407d14aa ???^M 0x893f908 _bfd_real_fopen^M /home/netbook/gdb/src/bfd/bfdio.c:178^M 0x89404d9 bfd_open_file^M /home/netbook/gdb/src/bfd/cache.c:596^M 0x894057a bfd_cache_lookup_worker^M /home/netbook/gdb/src/bfd/cache.c:261^M 0x89408a9 cache_bseek^M /home/netbook/gdb/src/bfd/cache.c:289^M 0x893fdc6 bfd_seek^M /home/netbook/gdb/src/bfd/bfdio.c:459^M 0x8946359 _bfd_generic_get_section_contents^M /home/netbook/gdb/src/bfd/libbfd.c:1069^M 0x8684f0b _Z23gdb_bfd_scan_elf_dyntagiP3bfdPyS1_^M /home/netbook/gdb/src/gdb/solib.c:1602^M 0x867d3d6 elf_locate_base^M /home/netbook/gdb/src/gdb/solib-svr4.c:707^M 0x867d6fa svr4_iterate_over_objfiles_in_search_order^M /home/netbook/gdb/src/gdb/solib-svr4.c:3430^M 0x86dc33f find_main_name^M /home/netbook/gdb/src/gdb/symtab.c:6283^M 0x86e3818 _Z13main_languagev^M /home/netbook/gdb/src/gdb/symtab.c:6313^M 0x86ce4d3 _Z20set_initial_languagev^M /home/netbook/gdb/src/gdb/symfile.c:1700^M 0x86d535d _Z19symbol_file_commandPKci^M /home/netbook/gdb/src/gdb/symfile.c:1681^M 0x82de824 file_command^M /home/netbook/gdb/src/gdb/exec.c:554^M 0x81d29aa _Z8cmd_funcP16cmd_list_elementPKci^M /home/netbook/gdb/src/gdb/cli/cli-decode.c:2735^M 0x872b56b _Z15execute_commandPKci^M /home/netbook/gdb/src/gdb/top.c:575^M 0x82dab44 _Z15command_handlerPKc^M /home/netbook/gdb/src/gdb/event-top.c:552^M 0x82dbaf8 _Z20command_line_handlerOSt10unique_ptrIcN3gdb13xfree_deleterIcEEE^M /home/netbook/gdb/src/gdb/event-top.c:788^M 0x82d9fe2 gdb_rl_callback_handler^M /home/netbook/gdb/src/gdb/event-top.c:259^M 0x88162dd rl_callback_read_char^M /home/netbook/gdb/src/readline/readline/callback.c:290^M 0x82da1dd gdb_rl_callback_read_char_wrapper_noexcept^M /home/netbook/gdb/src/gdb/event-top.c:195^M 0x82da38e gdb_rl_callback_read_char_wrapper^M /home/netbook/gdb/src/gdb/event-top.c:234^M 0x8765e37 stdin_event_handler^M /home/netbook/gdb/src/gdb/ui.c:155^M 0x8d575ab handle_file_event^M /home/netbook/gdb/src/gdbsupport/event-loop.cc:573^M 0x8d57cb4 gdb_wait_for_event^M /home/netbook/gdb/src/gdbsupport/event-loop.cc:694^M 0x8d58407 _Z16gdb_do_one_eventi^M /home/netbook/gdb/src/gdbsupport/event-loop.cc:264^M 0x8435953 start_event_loop^M /home/netbook/gdb/src/gdb/main.c:412^M 0x8435953 captured_command_loop^M /home/netbook/gdb/src/gdb/main.c:476^M 0x84379b4 captured_main^M /home/netbook/gdb/src/gdb/main.c:1320^M 0x84379b4 _Z8gdb_mainP18captured_main_args^M /home/netbook/gdb/src/gdb/main.c:1339^M 0x806177a main^M /home/netbook/gdb/src/gdb/gdb.c:32^M ... This is likely a dup of the thread sanitizer issues we're seeing in the test-case, but filing it FTR. In case it matter: ubuntu 14.04.6 i686, glibc 2.19. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-07-31 16:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-31 16:36 vries at gcc dot gnu.org [this message] 2023-08-02 17:27 ` [Bug symtab/30707] " vries at gcc dot gnu.org 2023-08-04 16:44 ` 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-30707-4717@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).