From: Elena Zannoni <ezannoni@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Set ADDR
Date: Wed, 21 Aug 2002 18:01:00 -0000 [thread overview]
Message-ID: <15716.14179.254954.85064@localhost.redhat.com> (raw)
In-Reply-To: <3D63B550.4010807@ges.redhat.com>
Andrew Cagney writes:
> PS: If anyone things this is just a PPC bug:
>
> (top-gdb) info registers
> eax 0xbffff864 -1073743772
> ecx 0x0 0
> ...
> (top-gdb) set $ecx = 0
> (top-gdb) info registers
> eax 0x0 0
> ecx 0x0 0
> ...
>
> So I guess two things:
>
> - GDB's testsuite doesn't cover this
The altivec-regs.exp file covers this, and, soon, a booke-regs.exp.
But nothing else.
> - Someone modifying a register or register variable is a pretty rare
> occurance
>
Yeah. I noticed this failure last night while retesting the booke code,
but by morning it was fixed! Miracle!
> Perhaphs I should add a sleep(1) to the value write code and see how
> long it takes someone to notice that ;-)
>
> enjoy,
> Andrew
prev parent reply other threads:[~2002-08-22 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 20:33 Andrew Cagney
2002-08-21 8:44 ` Andrew Cagney
2002-08-21 18:01 ` Elena Zannoni [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=15716.14179.254954.85064@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb-patches@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