From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
Subject: Re: Testsuite failures in gdb.base/callfuncs.exp
Date: Thu, 08 Feb 2007 17:03:00 -0000 [thread overview]
Message-ID: <20070208170309.GA14405@nevyn.them.org> (raw)
In-Reply-To: <je4pq58njs.fsf@sykes.suse.de>
On Fri, Feb 02, 2007 at 12:29:11AM +0100, Andreas Schwab wrote:
> Mark Kettenis <mark.kettenis@xs4all.nl> writes:
>
> > No I think there actually is a problem. Either the bspstore matters
> > or it doesn't. If it doesn't, GDB should just not include it in the
> > list of registers it displays. If it does matter, the test is showing
> > a genuine bug.
>
> I don't think a register should be left out just because it is read-only.
> It is still part of the processor state and can present information that
> may be needed for debugging.
Then can we avoid corrupting it, e.g. by adjusting both registers in a
way that lets us write arbitrary values to it?
I'm going to let you and Mark sort this out; I don't have a strong
opinion.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-02-08 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 12:33 Andreas Schwab
2007-01-31 12:49 ` Daniel Jacobowitz
2007-01-31 13:56 ` Andreas Schwab
2007-01-31 14:15 ` Daniel Jacobowitz
2007-01-31 14:57 ` Andreas Schwab
2007-01-31 15:10 ` Daniel Jacobowitz
2007-01-31 15:35 ` Andreas Schwab
2007-01-31 15:40 ` Daniel Jacobowitz
2007-02-01 22:53 ` Mark Kettenis
2007-02-01 23:29 ` Andreas Schwab
2007-02-08 17:03 ` 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=20070208170309.GA14405@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=schwab@suse.de \
/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