From: Michael Snyder <msnyder@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: Michael Snyder <msnyder@cygnus.com>,
gdb-patches@sources.redhat.com, rearnsha@arm.com
Subject: Re: [RFA] Disable "remote_rdp_can_run"
Date: Wed, 08 May 2002 11:35:00 -0000 [thread overview]
Message-ID: <3CD96CE8.C7066D8A@redhat.com> (raw)
In-Reply-To: <200205081520.QAA17365@cam-mail2.cambridge.arm.com>
Richard Earnshaw wrote:
>
> >
> > Happened across this. It's not right.
> >
> > With this in place, if you have not attached to your rdp target
> > (ie. by saying "target rdp"), but you instead just say "run",
> > gdb will attempt to use the rdp target, which has not at this
> > point been opened or initialized. This is not the right way
> > to make a remote target accept the "run" command.
> >
> > 2002-05-02 Michael Snyder <msnyder@redhat.com>
> >
> > * remote-rdp.c (remote_rdp_can_run): Return false. This is
> > not a good work-around for making a remote target accept 'run'.
> >
>
> I'm not sure I understand this. Shouldn't remote_rdp_can_run return 1
> once the target has been attached? If not, then I think the whole
> function should be killed (so that we pick up the default behaviour).
Actually, I agree with the second statement (it sound be killed).
If you want to have it return true once the target is attached,
you need some way of detecting that state (perhaps a global).
I didn't bother to do that, because I don't like the idea.
This is the only remote target that tries to do this.
I'd be glad to yank it if you say the word...
next prev parent reply other threads:[~2002-05-08 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 16:31 Michael Snyder
2002-05-08 8:21 ` Richard Earnshaw
2002-05-08 11:35 ` Michael Snyder [this message]
2002-05-08 12:11 ` Richard Earnshaw
2002-05-09 11:45 ` Michael Snyder
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=3CD96CE8.C7066D8A@redhat.com \
--to=msnyder@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.com \
--cc=rearnsha@arm.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