Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@wasabisystems.com>
To: Jim Blandy <jimb@redhat.com>
Cc: "Nathan J. Williams" <nathanw@wasabisystems.com>,
	gdb-patches@sources.redhat.com
Subject: Re: RFA: assert that target_fetch_registers did its job
Date: Sat, 07 Aug 2004 01:47:00 -0000	[thread overview]
Message-ID: <m3y8kroh27.fsf@gossamer.airs.com> (raw)
In-Reply-To: <vt2llgrrg22.fsf@zenia.home>

Jim Blandy <jimb@redhat.com> writes:

> Perhaps another option would be something like the below: it informs
> users that things are not as they seem, and encourages developers to
> fix up their targets.  Comments?

Aren't users going to wind up getting this error message approximately
one gazillion times when doing debugging on a target which doesn't
provide all the registers?

I don't know if this is the right approach in general, but if it is I
think it at least needs a static flag or something to only issue the
error once per execution.

I'm not sure this is the right approach because I don't see how to
avoid the error, at least not with something like BSD KVM.  The
registers are in the target, but the values just aren't available.
It's not like there is any way to fix that.

Ian


  reply	other threads:[~2004-08-07  1:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 23:00 Jim Blandy
2004-07-24  0:45 ` Daniel Jacobowitz
2004-08-03 14:23   ` Andrew Cagney
2004-08-07 18:42     ` Daniel Jacobowitz
2004-08-07 18:54       ` Andrew Cagney
2004-08-04 17:51   ` Jim Blandy
2004-08-06 20:50 ` Nathan J. Williams
2004-08-06 23:43   ` Jim Blandy
2004-08-07  1:47     ` Ian Lance Taylor [this message]
2004-08-07 16:13       ` Andrew Cagney
2004-08-07 18:31         ` Jim Blandy

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=m3y8kroh27.fsf@gossamer.airs.com \
    --to=ian@wasabisystems.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=nathanw@wasabisystems.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