This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/16822] Segmentation fault on add-symbol-file command
- From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 09 Apr 2014 02:27:31 +0000
- Subject: [Bug gdb/16822] Segmentation fault on add-symbol-file command
- Auto-submitted: auto-generated
- References: <bug-16822-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16822
Yao Qi <qiyao at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |qiyao at gcc dot gnu.org
--- Comment #1 from Yao Qi <qiyao at gcc dot gnu.org> ---
(In reply to Ulises Brindis from comment #0)
> Using GDB version 7.7 compiled with --host=arm-linux-gnueabi and
> --target=tic6x-ti-elf there is a segmentation fault when attempting to add a
> symbol file generated by TI C6x compiler version 7.4.4. I did not notice the
> segmentation fault in GDB version 7.2.
tic6x-*-* target was added in FSF GDB 7.4. GDB 7.2 with tic6x target shouldn't
be an official FSF release.
>
> Debugging into GDB a bit I notice that the seg fault comes from
> dwarf2read.c. On line 8464 the function dwarf2_attr returns a non-null but
> unusable attr. I have searched through my symbol file and I notice that for
> the specific DIE, there is no DW_AT_MIPS_linkage_name specified. I suspect
> that the null detecting condition needs reworking (line 8472 in
> dwarf2read.c). This then causes gdb_demangled to be called with a bad
> argument. I am not exactly sure how to fix this issue, so I am posting it
> here.
We need a reproducer to see the root cause of this problem. It may be a GDB
problem or a compiler problem. If possible, please attach a small executable
to cause GDB segmentation fault, and list your steps.
--
You are receiving this mail because:
You are on the CC list for the bug.