Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Carsten Lange <Carsten.Lange@detewe.de>
Cc: linux-mips@linux-mips.org
Subject: Re: gdbserver (gdb 5.2) with thread supprt
Date: Thu, 5 Sep 2002 09:29:17 -0400	[thread overview]
Message-ID: <20020905132917.GA13975@nevyn.them.org> (raw)
In-Reply-To: <3D76FEE7.D1DA2D99@detewe.de>

On Thu, Sep 05, 2002 at 08:51:19AM +0200, Carsten Lange wrote:
> Hi,
> 
> gdbserver from gdb 5.2 does not work for applications using threads, for others it
> works fine.
> 
> I wonder whether gdbserver supports threads and what I have to do to set it up
> (e.g where to get the
> patch)?
> 
> Any hints?

GDB CVS repository, of course.  I added thread support in June.  It
will be in 5.3, and 5.3 snapshots should start showing up on
sources.redhat.com/pub/gdb/ tomorrow.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

      reply	other threads:[~2002-09-05 13:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05  6:51 gdbserver (gdb 5.2) with thread supprt Carsten Lange
2002-09-05 13:29 ` 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=20020905132917.GA13975@nevyn.them.org \
    --to=dan@debian.org \
    --cc=Carsten.Lange@detewe.de \
    --cc=linux-mips@linux-mips.org \
    /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