public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug ada/25837] [cc-with-debug-names] gdb.ada/big_packed_array segv
Date: Fri, 17 Apr 2020 21:11:35 +0000	[thread overview]
Message-ID: <bug-25837-4717-VK6Ubk7UxS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25837-4717@http.sourceware.org/bugzilla/>

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

--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
The issue in that regression seems to be that the
symbol is defined for C, not Ada, so it isn't matched.
Maybe the DWARF reader should be creating an Ada
symbol here.

 <2><154e>: Abbrev Number: 3 (DW_TAG_subprogram)
    <154f>   DW_AT_external    : 1
    <154f>   DW_AT_name        : (indirect string, offset: 0x21d8):
foo_h731_021__c_func
    <1553>   DW_AT_decl_file   : 1
    <1554>   DW_AT_decl_line   : 17
    <1555>   DW_AT_decl_column : 14
    <1556>   DW_AT_linkage_name: (indirect string, offset: 0x201d):
MixedCaseFunc
    <155a>   DW_AT_declaration : 1


I didn't debug here but I assume the "declaration" setting
is preventing this.  But maybe it shouldn't when the name
and the mangled name are clearly different.


Or maybe I should just try to understand why the patch in
question could even cause this regression.  It doesn't seem
like that should be possible.

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

  parent reply	other threads:[~2020-04-17 21:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 14:26 [Bug ada/25837] New: " vries at gcc dot gnu.org
2020-04-17  6:50 ` [Bug ada/25837] " vries at gcc dot gnu.org
2020-04-17 20:13 ` tromey at sourceware dot org
2020-04-17 20:14 ` tromey at sourceware dot org
2020-04-17 20:16 ` tromey at sourceware dot org
2020-04-17 20:26 ` tromey at sourceware dot org
2020-04-17 21:11 ` tromey at sourceware dot org [this message]
2020-04-17 22:38 ` brobecker at gnat dot com
2020-04-21 15:15 ` tromey at sourceware dot org
2020-04-21 18:51 ` vries at gcc dot gnu.org
2020-04-23 13:22 ` cvs-commit at gcc dot gnu.org
2020-04-23 13:26 ` tromey at sourceware dot org

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-25837-4717-VK6Ubk7UxS@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).