linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hatle <fray@mvista.com>
To: Rick Hunnicutt <rhunnicu@getntds.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: GDB/GDBSERVER and remote Thread Debugging
Date: Thu, 06 Jun 2002 11:14:44 -0500	[thread overview]
Message-ID: <3CFF8A74.E17E25D2@mvista.com> (raw)
In-Reply-To: 3CFF865B.4C4F8DDA@mvista.com


Sorry, I was incorrect.  Remote thread debugging has not yet been pulled in by
the upstream GDB.  We have it internally, but it's not in GDB 5.2.  (Mind you
GDB 5.2 does have good local thread debugging.)

--Mark

Mark Hatle wrote:
>
> Probably not the answer you want, but MontaVista's GDB 5.2 version allows remote
> thread debugging.  (We are in the process of releasing GDB 5.2 as an update
> right now.  I don't know for sure when it will be released.)  I don't know if
> the upstream (GNU version) supports that for PPC or not.  I know it does not for
> SH, MIPS, and ARM.
>
> --Mark
>
> Rick Hunnicutt wrote:
> >
> > Will this give thread debugging with GDBSERVER as well or does it still have
> > to be native GDB?
> > >
> > > You will need to be working with GDB version 5.2 or newer to do thread
> > > debugging.
> > >
> > > --Mark
> > >
> > > > I'm looking for a stable GDB/GDBSERVER extension
> > > > suitable for (remote) Debugging multiple threads.
> > > >
> > > > It should also possible to attach already running
> > > > threads.
> > > >
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-06 16:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06 13:29 GDB/GDBSERVER and remote Thread Debugging Steffen Rumler
2002-06-06 15:14 ` Mark Hatle
2002-06-06 15:43   ` Rick Hunnicutt
2002-06-06 15:57     ` Mark Hatle
2002-06-06 16:14       ` Mark Hatle [this message]
2002-06-21 14:41   ` Lionel TAILLURAT

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=3CFF8A74.E17E25D2@mvista.com \
    --to=fray@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rhunnicu@getntds.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 NNTP newsgroup(s).