From: Daniel Jacobowitz <drow@mvista.com>
To: "G. Helffrich" <george@gly.bris.ac.uk>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Patches to improve Fortran support in gdb
Date: Tue, 28 May 2002 08:59:00 -0000 [thread overview]
Message-ID: <20020528155836.GA12301@branoic.them.org> (raw)
In-Reply-To: <200205281050.LAA00783@xterm1.gly.bris.ac.uk>
On Tue, May 28, 2002 at 11:50:38AM +0100, G. Helffrich wrote:
>
> Dear GDBers -
>
> I'm submitting these patches to 5.1.1 gdb to improve support for
> debugging of Fortran programs. The patches were initially developed
> on 4.16 gdb, and I ported them to 5.1.1.
>
> The patches fix bugs that are illustrated in the comments of the
> following Fortran program (compiled under g77 version 2.95.2 19991024 (release) (from FSF-g77 version 0.5.25 19991024 (release))).
>
> C Test program for gdb debugger. This illustrates gdb problems in Fortran
> C support in the following areas:
> C 1 - complex variable printing:
> C in gdb print cc ; print c
> C (garbage printed in gdb-4.16, gdb-5.1.1)
I don't have anything to say about the rest of these patches (except
that it would probably be better if you could separate them and submit
them one at a time); but I definitely object to this one, for the same
reasons we had an argument about it on the GDB list. The current code
is correct for several compiler versions. G77 should be changed to use
'R' unstead of the ambiguous 'r' symbol type.
> * gdb.1: update documentation to mention debugging Fortran language.
Does gdb.texinfo also need updating?
> Here are the patches themselves. FYI, I am already an FSF-registered
> contributor to g77.
FYI, I believe you'll need a separate assignment on file for GDB.
> Index: gdb-5.1.1/src/gdb/gdb.1
> ===================================================================
> RCS file: /usr/src/local/cvsroot/gdb-5.1.1/src/gdb/gdb.1,v
> retrieving revision 1.1.1.1
> retrieving revision 1.2
> diff -c -r1.1.1.1 -r1.2
> *** gdb-5.1.1/src/gdb/gdb.1 2002/02/02 11:34:20 1.1.1.1
> --- gdb-5.1.1/src/gdb/gdb.1 2002/05/22 12:25:15 1.2
> ***************
> *** 1,7 ****
> .\" Copyright 1991, 1999 Free Software Foundation, Inc.
> .\" See section COPYING for conditions for redistribution
> ! .\" $Id: gdb.1,v 1.1.1.1 2002/02/02 11:34:20 george Exp $
> ! .TH gdb 1 "4nov1991" "GNU Tools" "GNU Tools"
> .SH NAME
> gdb \- The GNU Debugger
> .SH SYNOPSIS
> --- 1,7 ----
> .\" Copyright 1991, 1999 Free Software Foundation, Inc.
> .\" See section COPYING for conditions for redistribution
> ! .\" $Id: gdb.1,v 1.2 2002/05/22 12:25:15 george Exp $
> ! .TH gdb 1 "22may2002" "GNU Tools" "GNU Tools"
> .SH NAME
> gdb \- The GNU Debugger
> .SH SYNOPSIS
> ***************
> *** 70,77 ****
> effects of one bug and go on to learn about another.
> .PP
>
> ! You can use GDB to debug programs written in C, C++, and Modula-2.
> ! Fortran support will be added when a GNU Fortran compiler is ready.
>
> GDB is invoked with the shell command \c
> .B gdb\c
> --- 70,76 ----
> effects of one bug and go on to learn about another.
> .PP
>
> ! You can use GDB to debug programs written in C, C++, Fortran and Modula-2.
>
> GDB is invoked with the shell command \c
> .B gdb\c
Heh. Quite outdated...
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-05-28 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 3:57 G. Helffrich
2002-05-28 8:59 ` Daniel Jacobowitz [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=20020528155836.GA12301@branoic.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=george@gly.bris.ac.uk \
/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