Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Arjan van Dijk <a.vandijk@phys.uu.nl>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: problem setting displays
Date: Fri, 13 Sep 2002 00:45:00 -0000	[thread overview]
Message-ID: <v03130302b9a73efeaa63@[131.211.32.140]> (raw)
In-Reply-To: <3D80E862.7000500@ges.redhat.com>

>That (in a sense) is good news.  It eliminates display from the problem.
>
>I suspect it is a problem in either the fortran (that was fortran right
>:-) parser or the code that handes fortran variable scopes.   The other
>possability is that GDB loaded in additional debug information (gdb does
>this when it first hits a breakpoint for an object file) and that made
>the expression invalid.


Hi,

Indeed it was fortran. Just plain g77, applied to a very simple example
program,  already makes the trouble. This makes me wonder why on earth the
two products, gdb and g77, both have a reference to GNU in their name, but
cannot collaborate. I find this very annoying. In a reaction to my second
attempt to get a reaction on this problem, Petr Sorfa <petrs@caldera.com>
gave me a reference to his project,
http://sourceforge.net/project/showfiles.php?group_id=56720
where he develops a gdb version which can handle Fortran (as long as the
compiler gives the right kind of debug info). In his gdb version (RC1), the
"print" command does not want to make a reference to a specific subroutine,
e.g. the command:

print subroutinename::variablename

does not (yet) work. Only "print variablename" works. This makes it
difficult to follow two variables both named "i" that are both involved in
a calculation, but which belong to different subroutines in the same
source-file (e.g. one calling the other). Also unfortunate is that this gdb
version does not compile on our Dec Alpha, but Petr already gave a
suggestion on how to try to solve this problem. On Linux it is a relief to
see this version simply eat the Fortran. I would be glad to see this
project be embraced by the maintainers of the official gdb distribution. So
far debugging Fortran is virtually impossible. I also wonder how the
Fortran community debugs its code. I fear that they all fall back on huge
amounts of write-statements and that they still live in the stone ages. Are
debuggers tools for quiche-eaters?

Regards,

Arjan


Arjan van Dijk
Institute for Marine and Atmospheric Research Utrecht
Faculty of Physics and Astronomy
Utrecht University
Princetonplein 5
NL - 3584 CC  Utrecht
The Netherlands

phone: +31 30 2532815
fax:   +31 30 2543163
e-mail: mailto:A.vanDijk@phys.uu.nl
homepage: http://www.phys.uu.nl/~vndijk



      reply	other threads:[~2002-09-13  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06  4:06 Arjan van Dijk
2002-09-06  6:08 ` Daniel Jacobowitz
2002-09-06  6:43   ` Arjan van Dijk
2002-09-12 12:17     ` Andrew Cagney
2002-09-13  0:45       ` Arjan van Dijk [this message]

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='v03130302b9a73efeaa63@[131.211.32.140]' \
    --to=a.vandijk@phys.uu.nl \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb@sources.redhat.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