public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/40040] gfortran invalid DW_AT_location for overridable variables
Date: Wed, 06 May 2009 10:55:00 -0000	[thread overview]
Message-ID: <20090506105424.27794.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40040-12292@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from jan dot kratochvil at redhat dot com  2009-05-06 10:54 -------
(In reply to comment #1)
> If DW_AT_location isn't provided, how would gdb find that address out?  Using
> DW_AT_MIPS_linkage_name (currently not emitted) and symbol lookup?

The GDB patch now assembles the symbol name from its parent DW_TAG_module as
`__modulename_MOD_varname'.  As GDB also has to know the C++ mangling rules I
believe this Fortran mangling is can be also used from GDB.

If GDB should never guess the fully qualified names I will have to file at
least one more GCC fortran debug/ PR for DW_TAG_imported_declaration which
already uses only DW_TAG_variable with DW_AT_declaration and no DW_AT_location.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40040


  parent reply	other threads:[~2009-05-06 10:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06  9:23 [Bug debug/40040] New: " jan dot kratochvil at redhat dot com
2009-05-06 10:25 ` [Bug debug/40040] " jakub at gcc dot gnu dot org
2009-05-06 10:55 ` jan dot kratochvil at redhat dot com [this message]
2009-05-06 16:42 ` burnus at gcc dot gnu dot org
2009-05-06 19:45 ` roland at redhat dot com
2009-05-06 20:13 ` jan dot kratochvil at redhat dot com
2009-08-21 18:40 ` burnus at gcc dot gnu dot org
2010-04-20  9:14 ` jan dot kratochvil at redhat dot com
2010-04-20  9:21 ` jakub at gcc dot gnu dot org
2010-04-20 12:24 ` jan dot kratochvil at redhat dot com
2010-04-21 10:31 ` jakub at gcc dot gnu dot org
2010-04-21 10:39 ` fxcoudert at gcc dot gnu dot org
2010-04-21 10:43 ` jakub at gcc dot gnu dot org
2010-04-21 10:46 ` fxcoudert at gcc dot gnu dot org
2010-04-21 16:49 ` jakub at gcc dot gnu dot org
     [not found] <bug-40040-4@http.gcc.gnu.org/bugzilla/>
2013-06-25  9:15 ` dominiq at lps dot ens.fr

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=20090506105424.27794.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).