Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: Testsuite failures in gdb.base/callfuncs.exp
Date: Thu, 01 Feb 2007 23:29:00 -0000	[thread overview]
Message-ID: <je4pq58njs.fsf@sykes.suse.de> (raw)
In-Reply-To: <200702012253.l11MrYDH006566@brahms.sibelius.xs4all.nl> (Mark 	Kettenis's message of "Thu, 1 Feb 2007 23:53:34 +0100 (CET)")

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.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2007-02-01 23:29 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 [this message]
2007-02-08 17:03               ` Daniel Jacobowitz

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=je4pq58njs.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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