Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Wu Zhou <woodzltc@cn.ibm.com>
To: Thomas Koenig <Thomas.Koenig@online.de>
Cc: Paul Thomas <paulthomas2@wanadoo.fr>,
	"'fortran@gcc.gnu.org'" <fortran@gcc.gnu.org>,
	gdb@sources.redhat.com
Subject: Debugging support - Re: g77 features lacking in gfortran - PR19292
Date: Tue, 25 Oct 2005 16:43:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.63.0510251357330.17274@linux.site> (raw)
In-Reply-To: <20051022233015.GA6615@meiner.onlinehome.de>

Hi Thomas,

On Sun, 23 Oct 2005, Thomas Koenig wrote:

> On Sat, Oct 22, 2005 at 08:14:50AM +0200, Paul Thomas wrote:
> 
> > >22244 dimension information is lost for multi-dimension array - 
> > >primarily gdb and optimization problem.
> 
> I think that one's fairly important.  I wouldn't call debugging
> support OK if you can't look at arrays properly.  Unfortunately,
> I don't even have the first idea to where I should start looking to
> fix this...

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...

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?  Part of my effort 
is to extend gdb's testsuite with reference to gfortran compiler.  So I am 
very happy to receive any feedback on these.  Thanks a lot in advance.

Best Regards
- Wu Zhou  


       reply	other threads:[~2005-10-25 16:43 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 [this message]
2005-10-25 19:59     ` Thomas Koenig
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=Pine.LNX.4.63.0510251357330.17274@linux.site \
    --to=woodzltc@cn.ibm.com \
    --cc=Thomas.Koenig@online.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=paulthomas2@wanadoo.fr \
    /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