From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Another Fortran problem...
Date: Fri, 26 Oct 2007 13:14:00 -0000 [thread overview]
Message-ID: <20071026131357.GA17240@caradoc.them.org> (raw)
In-Reply-To: <19c433eb0710260604g53552b55ree7c72b13cb27f62@mail.gmail.com>
On Fri, Oct 26, 2007 at 02:04:56PM +0100, Fran?ois-Xavier Coudert wrote:
> What I would consider the best behaviour for gdb is that it considers
> both source names and linkage names, and in case of an ambiguity
> 1. between a source name and a linkage name, go for the linkage name
> 2. between two source names, ask the user to specify the linkage
> name of one of them
>
> Of course, I don't know how hard it would be to implement this behaviour.
Somewhat impractical. I think we would be best off ignoring linkage
names for Fortran, or else GCC not emitting them... I don't know
which. Won't they generally match the names in the ELF symbol table?
In that case they are not particularly useful for definitions.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-26 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 10:39 François-Xavier Coudert
2007-10-26 12:03 ` Daniel Jacobowitz
2007-10-26 13:05 ` François-Xavier Coudert
2007-10-26 13:14 ` Daniel Jacobowitz [this message]
2007-10-26 13:58 ` François-Xavier Coudert
2007-10-26 14:06 ` Daniel Jacobowitz
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=20071026131357.GA17240@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@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).