From: Thomas Koenig <Thomas.Koenig@online.de>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: Thomas Koenig <Thomas.Koenig@online.de>,
Paul Thomas <paulthomas2@wanadoo.fr>,
"'fortran@gcc.gnu.org'" <fortran@gcc.gnu.org>,
gdb@sources.redhat.com
Subject: Re: Debugging support - Re: g77 features lacking in gfortran - PR19292
Date: Tue, 25 Oct 2005 19:59:00 -0000 [thread overview]
Message-ID: <20051025195908.GA5960@meiner.onlinehome.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0510251357330.17274@linux.site>
On Tue, Oct 25, 2005 at 02:18:33PM +0800, Wu Zhou wrote:
> GDB also has some other problems while working with gfortran, such as the
> printing of one-dimensional array, function evaluation, handling of common
> block variable and so on...
... variables from modules (I've just reported this as PR 24526),
allocatable arrays (PR 17905) and so on.
>
> Some of these problems stems from the DWARF output of gfortran, some lies
> in the code of gdb, some might involve both. I has been working on some
> of these problem at gdb's side. I am now thinking of whether there are
> any specific requirement from gfortran community for GDB. Did any of you
> have a big picture about how well gdb work with gfortran? Did you
> have a list of things that want GDB to support first?
My (personal) vote would go to supporting arrays (one- and
multidimensional) (PR 22244) should be pretty hight on the list,
followed by variables in common blocks (PR 23057).
Any help you can provide is certainly very welcome!
Thomas
next prev parent reply other threads:[~2005-10-25 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4359D8DA.10003@wanadoo.fr>
[not found] ` <20051022233015.GA6615@meiner.onlinehome.de>
2005-10-25 16:43 ` Wu Zhou
2005-10-25 19:59 ` Thomas Koenig [this message]
2005-10-26 3:44 ` Wu Zhou
2005-10-26 18:19 ` Thomas Koenig
2005-10-27 2:21 ` Wu Zhou
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=20051025195908.GA5960@meiner.onlinehome.de \
--to=thomas.koenig@online.de \
--cc=fortran@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=paulthomas2@wanadoo.fr \
--cc=woodzltc@cn.ibm.com \
/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