Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: "Sarnath K - CTD, Chennai." <k_sarnath@ctd.hcltech.com>,
	gdb@sources.redhat.com
Subject: Re: Thread Support for remote debugging
Date: Thu, 31 Jan 2002 17:18:00 -0000	[thread overview]
Message-ID: <20020131201847.A8691@nevyn.them.org> (raw)
In-Reply-To: <3C59D46C.AF35262A@redhat.com>

On Thu, Jan 31, 2002 at 03:34:04PM -0800, Michael Snyder wrote:
> Daniel Jacobowitz wrote:
> > 
> > On Thu, Jan 31, 2002 at 12:40:34PM -0800, Michael Snyder wrote:
> > > "Sarnath K - CTD, Chennai." wrote:
> > > >
> > > > Hi,
> > > >  I have been browsing the mail archives for
> > > > knowing the current state of thread support
> > > > while doing remote debugging using GDB.
> > > >  Although a lot of discussions have happened,
> > > > I am not able to find the current state of work
> > > > in that area.
> > >
> > > By "knowing the current state of thread support",
> > > do you mean finding out whether the remote target
> > > supports thread debugging?
> > 
> > No, he means "knowing whether GDB and GDB Server support doing remote
> > debugging at all", as far as I can tell.
> 
> Yeah, but gdb always supports doing remote thread debugging, 
> so the question comes down to whether gdbserver (ie. the 
> remote target, as I said) supports thread debugging.
> 
> > We've covered this ground a couple times lately :)  Someone promised to
> > contribute thread support and dropped off the face of the earth.  It's
> > on my TODO list, but I don't anticipate getting to it any time soon.
> 
> I trust you mean in gdbserver.  The support for remote threads
> is already in gdb.

Yes, that's what I meant.  Sorry.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-02-01  1:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21  1:11 Sarnath K - CTD, Chennai.
2002-01-21  6:07 ` Daniel Jacobowitz
2002-01-21  7:10 ` Quality Quorum
2002-01-21  8:38   ` Andrew Cagney
2002-01-31 12:47 ` Michael Snyder
2002-01-31 15:12   ` Daniel Jacobowitz
2002-01-31 15:22     ` Quality Quorum
2002-01-31 17:22       ` Daniel Jacobowitz
2002-01-31 19:41         ` Quality Quorum
2002-01-31 19:29       ` Andrew Cagney
2002-01-31 19:44         ` Quality Quorum
2002-01-31 15:41     ` Michael Snyder
2002-01-31 17:18       ` Daniel Jacobowitz [this message]
2002-01-31 17:21         ` Michael Snyder
2002-01-21 22:08 Sarnath K - CTD, Chennai.
2002-01-31 23:32 Korbel, Michal
2002-02-01  7:45 ` Dan Kegel
2002-02-01  8:13 Korbel, Michal
2002-02-01  8:27 ` Dan Kegel
2002-02-01  9:43   ` Quality Quorum

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=20020131201847.A8691@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=k_sarnath@ctd.hcltech.com \
    --cc=msnyder@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