From: Daniel Jacobowitz <drow@mvista.com>
To: Dan Towner <dant@picochip.com>
Cc: gdb@sources.redhat.com
Subject: Re: The value of inferior_ptid for remote debugging targets
Date: Tue, 08 Oct 2002 11:13:00 -0000 [thread overview]
Message-ID: <20021008181419.GA29501@nevyn.them.org> (raw)
In-Reply-To: <3DA31C1D.2010708@picochip.com>
On Tue, Oct 08, 2002 at 06:55:41PM +0100, Dan Towner wrote:
> >Are you hitting the code in remote_open_1:
>
> No.
>
> >Or, it sounds like you're using your own remote protocol module. If so
> >that's probably the bit you're missing.
>
> I copied it from remote_e7000.c. Would it be missing from that as well?
> Do I have to explicitly set inferior_ptid with some sensible values?
Bad choice of example code. I recommend you read through remote_open_1
in remote.c. Yes, you do.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-10-08 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 10:30 Dan Towner
2002-10-08 10:36 ` Daniel Jacobowitz
2002-10-08 10:54 ` Dan Towner
2002-10-08 11:13 ` Daniel Jacobowitz [this message]
2002-10-11 17:51 ` core file Satya
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=20021008181419.GA29501@nevyn.them.org \
--to=drow@mvista.com \
--cc=dant@picochip.com \
--cc=gdb@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