[Bug gdb/27317] New: gdb crashes upon target remote :1234

[Bug gdb/27317] New: gdb crashes upon target remote :1234

[r.kloos at campus dot tu-berlin.de]

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

            Bug ID: 27317
           Summary: gdb crashes upon target remote :1234
           Product: gdb
           Version: 9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: r.kloos at campus dot tu-berlin.de
  Target Milestone: ---

Created attachment 13196
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13196&action=edit
core dump of gdb after described error

The following output is given after trying to use gdb with a symbol file and
trying to execute target remote :1234 :


Reading symbols from kernel_debug...
DW_FORM_strp pointing outside of .debug_str section [in module /<PATH TO FILE
OMITTED>/kernel_debug]
(No debugging symbols found in kernel_debug)
(gdb) target remote localhost:1234
Remote debugging using localhost:1234
../../gdb-9.2/gdb/dwarf2-frame.c:2004: internal-error: const gdb_byte*
decode_frame_entry_1(comp_unit*, const gdb_byte*, int, dwarf2_cie_table&,
dwarf2_fde_table*, eh_frame_type): Assertion `fde->cie != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

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

../../gdb-9.2/gdb/dwarf2-frame.c:2004: internal-error: const gdb_byte*
decode_frame_entry_1(comp_unit*, const gdb_byte*, int, dwarf2_cie_table&,
dwarf2_fde_table*, eh_frame_type): Assertion `fde->cie != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
Aborted (core dumped)


The symbol file should work, however I don't get why gdb would crash if it
didn't either.
I have included the core dump

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

[Bug gdb/27317] gdb crashes upon target remote :1234

[r.kloos at campus dot tu-berlin.de]

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

r.kloos at campus dot tu-berlin.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #13196|0                           |1
        is obsolete|                            |

--- Comment #1 from r.kloos at campus dot tu-berlin.de ---
Created attachment 13197
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13197&action=edit
Second core file generated with same behaviour since first one seemed very
small

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

[Bug gdb/27317] gdb crashes upon target remote :1234

[r.kloos at campus dot tu-berlin.de]

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

--- Comment #2 from r.kloos at campus dot tu-berlin.de ---
Core dumps have a bigger size on my system, maybe they get compressed upon
upload?

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

[Bug gdb/27317] gdb crashes upon target remote :1234

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org
   Last reconfirmed|                            |2022-03-06
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |WAITING

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
A core dump of gdb isn't super useful, because it's specific
to your build of gdb.  The failing executable might be useful
if the problem can be reproduced without any special setup
(maybe not in this case).  A stack trace from gdb itself might
also be informative.

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

[Bug gdb/27317] gdb crashes upon target remote :1234

[r.kloos at campus dot tu-berlin.de]

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

--- Comment #4 from r.kloos at campus dot tu-berlin.de ---
Created attachment 14008
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14008&action=edit
Backtrace from the gdb executable in question

Here would be the backtrace of the presumably buggy executable

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

[Bug gdb/27317] gdb crashes upon target remote :1234

[r.kloos at campus dot tu-berlin.de]

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

--- Comment #5 from r.kloos at campus dot tu-berlin.de ---
(In reply to Tom Tromey from comment #3)
> A core dump of gdb isn't super useful, because it's specific
> to your build of gdb.  The failing executable might be useful
> if the problem can be reproduced without any special setup
> (maybe not in this case).  A stack trace from gdb itself might
> also be informative.

Apart from the backtrace I could also upload the executable, but I am not sure
if it would be helpful without the rest of the code.
It's kernel code from a university course running on qemu, so reproducing the
bug would need a special setup software wise.

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