public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.brass at desy dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/22424] gdb.lookup_type fails for Fortran
Date: Mon, 22 Feb 2021 10:34:50 +0000	[thread overview]
Message-ID: <bug-22424-4717-UeGgHWo5GU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22424-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Simon Braß <simon.brass at desy dot de> ---
(In reply to Simon Braß from comment #2)
> Created attachment 12325 [details]
> Include Fortran veto on symbol_matches_domain
> 
> I've bumped into this problem today.
> 
> I tried looking up the solution from bug 21763:
> In symtab.c's symbol_matches_domain, it seems that symbol_domain and domain
> do not match (d'uh) for the derived type lookup.
> 
> I've then looked up the definition of my derived type in the dwarf output of
> gfortran, and found that the derived is tagged as DW_TAG_structure_type
> (would go into STRUCT_DOMAIN), not as DW_TAG_typedef (would go into
> VAR_DOMAIN), as one could maybe expect?
> 
> The information about the type should then be searched in STRUCT_DOMAIN and
> not in VAR_DOMAIN, or not?
> 
> Adding an exception for language_fortran in symtab.c's symbol_matches_domain
> seems to resolve the problem (however, I did not run the testsuite).

Is there any progress regarding this bug? E.g. general progress on the Fortran
support?

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

           reply	other threads:[~2021-02-22 10:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-22424-4717@http.sourceware.org/bugzilla/>]

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-22424-4717-UeGgHWo5GU@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).