public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "faraz.abrar9 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/26549] New: GDB crashes when performing `backtrace` on a binary with full symbols enabled
Date: Fri, 28 Aug 2020 16:40:51 +0000	[thread overview]
Message-ID: <bug-26549-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26549

            Bug ID: 26549
           Summary: GDB crashes when performing `backtrace` on a binary
                    with full symbols enabled
           Product: gdb
           Version: 9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: backtrace
          Assignee: unassigned at sourceware dot org
          Reporter: faraz.abrar9 at gmail dot com
  Target Milestone: ---

Hello,

This issue is very recent. I have built GDB 9.2 (downloaded from
https://ftp.gnu.org/gnu/gdb/gdb-9.2.tar.xz) and tried to run V8 built with full
debugging symbols. After running the interpreter, attempting to CTRL+C and
`backtrace` will cause the following error:

```
../../gdb/dwarf2read.c:5264: internal-error: compunit_symtab*
dw2_find_pc_sect_compunit_symtab(objfile*, bound_minimal_symbol, CORE_ADDR,
obj_section*, int): Assertion `result != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

This is a bug, please report it.  For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.

Aborted (core dumped)
```

The binary I was using can be found here (it is nearly 400MB):
https://drive.google.com/file/d/1JXlFh0ijrlWpj7XwOyxMO4-TorCXiCYt/view?usp=sharing

If you need more information, let me know :)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-08-28 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 16:40 faraz.abrar9 at gmail dot com [this message]
2020-08-29  8:17 ` [Bug backtrace/26549] " faraz.abrar9 at gmail dot com
2020-09-01 14:14 ` tromey at sourceware dot org
2021-05-27 10:09 ` jeanmichael.celerier at gmail dot com
2023-11-30 17:03 ` 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-26549-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: 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).