Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@allinea.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Peter Choi <peter_tkchoi@yahoo.com>, gdb@sources.redhat.com
Subject: Re: [NEED HELP] Problem to multithread remote debugging with GDBserver
Date: Thu, 27 Oct 2005 13:25:00 -0000	[thread overview]
Message-ID: <1130420692.1548.93.camel@cpc2-oxfd8-3-0-cust199.oxfd.cable.ntl.com> (raw)
In-Reply-To: <20051027124722.GB21596@nevyn.them.org>

On Thu, 2005-10-27 at 08:47 -0400, Daniel Jacobowitz wrote:
> On Thu, Oct 27, 2005 at 03:26:55AM -0700, Peter Choi wrote:
> > Hi,
> > 
> >   I've heard that GDB 5.3 onwards has supported remote
> > debugging multiple thread programs, but I still fail
> > to do so. I wonder what I have done wrong.
> 
> > First we set everything up and connect:
> > 
> >     (gdb) set solib-search-path
> > /usr/local/cris/r59/cris-axis-linux-gnu/lib/
> >     (gdb) set solib-absolute-prefix /dev/null/
> 
> First of all don't do that.  Use solib-absolute-prefix and make a host
> environment that looks like the target.  It's much more likely to work.
> 
> Second, you didn't mention until here that your target was cris.  It
> just takes a couple of lines to implement multithread support in
> gdbserver, but they have to be done for each port; I don't know if
> anyone has done that for cris yet.  In fact gdbserver didn't support
> cris until after the release of 6.3, so you should be using CVS.

Hi Daniel

A much asked question seems to be how do you implement multithread
support in gdbserver..   Where would you go about finding documentation
for this, my googling has only so far come up with an email from you of
about two years or so ago seeing we need some docs!  Is there a True
Definitive Guide?

Cheers
David




  reply	other threads:[~2005-10-27 13:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27 10:27 Peter Choi
2005-10-27 12:47 ` Daniel Jacobowitz
2005-10-27 13:25   ` David Lecomber [this message]
2005-10-27 13:50     ` Daniel Jacobowitz
2005-10-28  1:55   ` Peter Choi
2005-10-28  3:05     ` Daniel Jacobowitz
2005-10-28  4:50   ` Peter Choi
2005-10-28  4:58   ` Peter Choi
2005-10-28 12:47     ` Daniel Jacobowitz
2005-10-31  1:51       ` Peter Choi
2005-10-31  4:20         ` 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=1130420692.1548.93.camel@cpc2-oxfd8-3-0-cust199.oxfd.cable.ntl.com \
    --to=david@allinea.com \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=peter_tkchoi@yahoo.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