[Bug backtrace/26549] New: GDB crashes when performing `backtrace` on a binary with full symbols enabled

[Bug backtrace/26549] New: GDB crashes when performing `backtrace` on a binary with full symbols enabled

[faraz.abrar9 at gmail dot com]

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.

[Bug backtrace/26549] GDB crashes when performing `backtrace` on a binary with full symbols enabled

[faraz.abrar9 at gmail dot com]

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

--- Comment #1 from Faith <faraz.abrar9 at gmail dot com> ---
I checked and confirmed that the issue is with the gdb `index` section that is
added at build time. V8 actually comes with a tool that lets you remove the
index. You can run it by doing the following from the V8 root directory:

`build/gdb-add-index -r out/x64.release/d8`

Replace the last parameter with the path to the `d8` binary, and it'll remove
the index section. This does indeed solve the issue.

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

[Bug backtrace/26549] GDB crashes when performing `backtrace` on a binary with full symbols enabled

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
Could you possibly try gdb from git?
I don't know whether it will work or not, but it would
be nice to find out.

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

[Bug backtrace/26549] GDB crashes when performing `backtrace` on a binary with full symbols enabled

[jeanmichael.celerier at gmail dot com]

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

Jean-Michaël Celerier <jeanmichael.celerier at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeanmichael.celerier@gmail.
                   |                            |com

--- Comment #3 from Jean-Michaël Celerier <jeanmichael.celerier at gmail dot com> ---
Hello,
I'm encountering the same issue with gdb 10.2, but I'm not using --gdb-index

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

[Bug backtrace/26549] GDB crashes when performing `backtrace` on a binary with full symbols enabled

[tromey at sourceware dot org]

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

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Jean-Michaël Celerier from comment #3)
> Hello,
> I'm encountering the same issue with gdb 10.2, but I'm not using --gdb-index

I think it's probably a separate issue then.
However - can you try a newer gdb?
I feel like there were some bug fixes in this area.

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