Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Arthur H. Edwards, 1, 505-853-6042, 505-256-0834" <edwards@icantbelieveimdoingthis.com>
To: gdb@sources.redhat.com, edwards@icantbelieveimdoingthis.com
Subject: misrepresentation of complex numbers
Date: Mon, 26 Nov 2001 12:37:00 -0000	[thread overview]
Message-ID: <3C02A11A.2040709@icantbelieveimdoingthis.com> (raw)

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
From gdb@thewrittenword.com Mon Nov 26 14:36:00 2001
From: gdb@thewrittenword.com
To: gdb@sources.redhat.com
Subject: Re: GDB 5.1 on Tru64 UNIX 4.0D, 5.0, 5.1
Date: Mon, 26 Nov 2001 14:36:00 -0000
Message-id: <20011126163601.A28540@oolong.il.thewrittenword.com>
References: <20011126104505.A14474@oolong.il.thewrittenword.com> <2110-Mon26Nov2001211029+0200-eliz@is.elta.co.il> <20011126134826.A24100@oolong.il.thewrittenword.com> <1438-Mon26Nov2001223103+0200-eliz@is.elta.co.il>
X-SW-Source: 2001-11/msg00264.html
Content-length: 662

On Mon, Nov 26, 2001 at 10:31:04PM +0200, Eli Zaretskii wrote:
> > From: gdb@thewrittenword.com
> > Date: Mon, 26 Nov 2001 13:48:26 -0600
> > > 
> > > Search the file README for "alpha-dec-osf4", it's all there.
> > 
> > Are you sure?
> > 
> > $ cd gdb-5.1
> > $ grep -i alpha gdb/README
> > [no output]
> 
> Yes, I'm sure:
> 
> $ grep -i alpha gdb/README
> alpha-dec-osf5.1
> alpha-dec-osf4.0e
> 
> Here's the entry in its entirety:
> 
>     alpha-dec-osf4.0e
> 
>     GDB 5.1 is known to have problems on this platform (encounters an
>     internal error in the symbol table reader).

Oh well. Doesn't work for me.

-- 
albert chin (china@thewrittenword.com)


WARNING: multiple messages have this Message-ID
From: "Arthur H. Edwards,1,505-853-6042,505-256-0834" <edwards@icantbelieveimdoingthis.com>
To: gdb@sources.redhat.com, edwards@icantbelieveimdoingthis.com
Subject: misrepresentation of complex numbers
Date: Wed, 14 Nov 2001 13:45:00 -0000	[thread overview]
Message-ID: <3C02A11A.2040709@icantbelieveimdoingthis.com> (raw)
Message-ID: <20011114134500.csZUKmRxR_jjeKliaZ78xWsTm7OxUoHU-QlV1QqxOic@z> (raw)

[-- Attachment #1: Type: text/plain, Size: 291 bytes --]

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

[-- Attachment #2: testc.f --]
[-- Type: text/plain, Size: 144 bytes --]

	program t1
	implicit real*8(a-h,o-z)
	complex*16 s
	a = 2*5.0d0
	b = 2*2.0d0
	s=cmplx(a,b)
	write(6,3555) s
3555	format(5x,d20.10)
	stop
	end


             reply	other threads:[~2001-11-26 12:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 12:37 Arthur H. Edwards, 1, 505-853-6042, 505-256-0834 [this message]
2001-11-14 13:45 ` Arthur H. Edwards,1,505-853-6042,505-256-0834
2001-12-15 11:03 ` Andrew Cagney
2002-01-08  6:48   ` Petr Sorfa

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=3C02A11A.2040709@icantbelieveimdoingthis.com \
    --to=edwards@icantbelieveimdoingthis.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