This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: misrepresentation of complex numbers
- From: Petr Sorfa <petrs at caldera dot com>
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Cc: "Arthur H. Edwards,1,505-853-6042,505-256-0834" <edwards at icantbelieveimdoingthis dot com>, gdb at sources dot redhat dot com
- Date: Tue, 08 Jan 2002 09:53:15 -0500
- Subject: Re: misrepresentation of complex numbers
- Organization: Caldera
- References: <3C02A11A.2040709@icantbelieveimdoingthis.com> <3C1B9E97.9040706@cygnus.com>
- Reply-to: petrs at caldera dot com
Hi,
Sorry for the late reply (been away).
I don't think this is a bug. The output from the gdb print command for
certain FORTRAN values does not need to match the output from the
FORTRAN print statement. Consider arrays, particularly large
multi-dimensional ones, that become completely unreadble with the
FORTRAN print statment, but handled quite well with the gdb print
command.
In addition it is much easier to parse the output values provided by the
gdb print command.
Petr
> Thanks. If you haven't already, could you please create a bug report of
> this. See http://sources.redhat.com/gdb/bugs/
>
> Andrew
>
> > I attach a very simple code, testc.f that illustrates the bug in dbg. After compiling with the -g option stop the code at line 7 and issue the gdb command
> >
> > print s
> >
> > gdb will respond with
> >
> > $1 = (10,10)
> >
> > issue the cont command and you will see that the number should be
> >
> > 10, 4
> >
> >
> > Art Edwards
> >
> >
--
--------------------------------------------------------
Petr Sorfa Senior Software Engineer
Caldera
430 Mountain Ave. http://www.caldera.com
Murray Hill 07974
NJ, USA
--------------------------------------------------------
Disclaimer: All my comments are my own and nobody else's
----------------------------------------------------------