public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at inbox dot ru" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/25678] gdb crashes with "internal-error: sect_index_text not initialized" when .text missing and >2 segments Date: Wed, 27 May 2020 08:03:31 +0000 [thread overview] Message-ID: <bug-25678-4717-RftC63GoeJ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25678-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25678 --- Comment #8 from Sergei Trofimovich <slyfox at inbox dot ru> --- On gdb-9.2 test case from #comment1 fails as: """ $ x86_64-pc-linux-gnu-gcc test.c ./libtestcase.so $ gdb --quiet ./a.out Reading symbols from ./a.out... (gdb) r Starting program: /tmp/a.out ../../gdb-9.2/gdb/dwarf2read.c:8080: internal-error: sect_index_text not initialized A problem internal to GDB has been detected, further debugging may prove unreliable. """ -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-27 8:03 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-15 2:24 [Bug symtab/25678] New: " klkblake at gmail dot com 2020-04-02 10:12 ` [Bug symtab/25678] " thravran.qathy at gmail dot com 2020-04-02 10:17 ` thravran.qathy at gmail dot com 2020-04-02 15:51 ` keiths at redhat dot com 2020-04-10 16:14 ` thravran.qathy at gmail dot com 2020-05-14 20:05 ` mlimber at gmail dot com 2020-05-16 19:22 ` simark at simark dot ca 2020-05-27 7:58 ` slyfox at inbox dot ru 2020-05-27 8:03 ` slyfox at inbox dot ru [this message] 2020-09-19 18:49 ` cebtenzzre at gmail dot com 2020-09-19 19:40 ` cebtenzzre at gmail dot com 2020-09-20 1:31 ` simark at simark dot ca 2020-10-08 9:15 ` napth at protonmail dot com 2023-04-11 21:58 ` jreiser at BitWagon dot com 2023-08-25 16:48 ` dilfridge at gentoo dot org 2024-01-14 4:45 ` sam at gentoo dot org 2024-01-14 4:45 ` sam at gentoo 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-25678-4717-RftC63GoeJ@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).