public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Frank.Christ@RSBICK.rohde-schwarz.com
Cc: gdb@sources.redhat.com
Subject: Re: Antwort: Re: Re: Remote Debugging Of Multithreaded Application on PPC 82xx
Date: Mon, 17 Mar 2003 14:56:00 -0000	[thread overview]
Message-ID: <20030317145624.GA30612@nevyn.them.org> (raw)
In-Reply-To: <C1256CEC.005090EC.00@mail.rohde-schwarz.com>

On Mon, Mar 17, 2003 at 03:43:19PM +0100, Frank.Christ@RSBICK.rohde-schwarz.com wrote:
> Hi Daniel,
> 
> I am using glibc 2.1.3! Here is my remote log!
> The following two lines seem suspicious to me!
>      Packet Z0 (software-breakpoint) is NOT supported
>      binary downloading NOT suppported by target

That's normal.


> 
> Any hints regarding the remote log?

I believe you've hit an unavoidable problem in the current remote
protocol; when the client sends Hc0 followed by s, the stub has no way
to know which thread to step.  I've discussed this problem on the list
before and we've never reached a consensus about how to solve it.

Andrew, if you remember, this is the problem that my proposed "Hs"
packet was supposed to solve.  Hmm, rereading your last message on that
thread it looks like I dropped the ball.  You proposed something like
"HtPID,0;s"; I guess I'm not entirely sure what you wanted that to
mean.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

      reply	other threads:[~2003-03-17 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17 14:44 Frank.Christ
2003-03-17 14:56 ` 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=20030317145624.GA30612@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=Frank.Christ@RSBICK.rohde-schwarz.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).