public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/16822] Segmentation fault on add-symbol-file command
Date: Wed, 09 Apr 2014 02:27:00 -0000	[thread overview]
Message-ID: <bug-16822-4717-9fX5eDnyhx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16822-4717@http.sourceware.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.


  parent reply	other threads:[~2014-04-09  2:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 20:09 [Bug gdb/16822] New: Segmentation fault on add-symbol-file ubrindis at ti dot com
2014-04-08 20:10 ` [Bug gdb/16822] Segmentation fault on add-symbol-file command ubrindis at ti dot com
2014-04-09  2:27 ` qiyao at gcc dot gnu.org [this message]
2014-04-09 14:33 ` ubrindis at ti dot com
2014-04-09 14:35 ` ubrindis at ti dot com
2014-04-09 15:43 ` keiths at redhat dot com
2014-04-09 16:24 ` ubrindis at ti dot com
2014-04-10 18:47 ` c-addison at ti dot com
2015-05-18 11:29 ` thangaraj.ponnusamy at in dot bosch.com
2015-05-19  5:23 ` kleiber.tamas at gmail dot com
2015-05-20  5:52 ` thangaraj.ponnusamy at in dot bosch.com
2015-05-21  5:50 ` tony.liu at arm dot com
2015-09-24 21:38 ` kevinb at redhat dot com

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-16822-4717-9fX5eDnyhx@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).