This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/15325] New: crashes with "segmentation fault" for self-created dwarf-file
- From: "smarf at gmx dot de" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 30 Mar 2013 12:48:28 +0000
- Subject: [Bug gdb/15325] New: crashes with "segmentation fault" for self-created dwarf-file
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15325
Bug #: 15325
Summary: crashes with "segmentation fault" for self-created
dwarf-file
Product: gdb
Version: 7.5
Status: NEW
Severity: normal
Priority: P2
Component: gdb
AssignedTo: unassigned@sourceware.org
ReportedBy: smarf@gmx.de
Classification: Unclassified
Created attachment 6961
--> http://sourceware.org/bugzilla/attachment.cgi?id=6961
floppy disk image and dwarf debug info
I tried to build a dwarf-file for a bootable image (see attached file
floppy.img which can be started via "qemu -fda floppy.img -boot a -s"). This
dwarf-file (see attached file dwarf) seems to be ok for readelf and dwarfdump,
but not for gdb.
Starting gdb with "gdb --se=dwarf" and connecting to qemu with "target remote
:1234", I get "0x001045ea in ?? (warning: (Internal error: pc 0x1045ea in read
in psymtab, but not in symtab.)" from gdb 7.1 and "Segmentation fault" from gdb
7.5.1 without anything else.
I would expect gdb to recognize 0x1045ea as being in Kernel.main as "dwarfdump
-a -vv" shows
<0>< 11> DW_TAG_compile_unit <abbrev 1>
DW_AT_name Kernel
DW_AT_producer SJC
DW_AT_language DW_LANG_C
DW_AT_low_pc 0x104320
DW_AT_high_pc 0x108dd9
<0>< 30> DW_TAG_subprogram <abbrev 2>
DW_AT_name main
DW_AT_external yes(1)
DW_AT_low_pc 0x104320
DW_AT_high_pc 0x1045ed
I think giving "Segmentation fault" is a bug in gdb. Additionally, if anyone
can suggest changes to get gdb accepting it, I would be very happy.
Thanks in advance! :-)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.