linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hatle <fray@mvista.com>
To: Steffen Rumler <Steffen.Rumler@icn.siemens.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: GDB/GDBSERVER and remote Thread Debugging
Date: Thu, 06 Jun 2002 10:14:48 -0500	[thread overview]
Message-ID: <3CFF7C68.C6151B82@mvista.com> (raw)
In-Reply-To: 3CFF63A7.375F0644@icn.siemens.de


You will need to be working with GDB version 5.2 or newer to do thread
debugging.

--Mark

Steffen Rumler wrote:
>
> Hello,
>
> I'm looking for a stable GDB/GDBSERVER extension
> suitable for (remote) Debugging multiple threads.
>
> It should also possible to attach already running
> threads.
>
> Actually I'm working with the GDB 5.0, but
> I have problems with it. Sometimes breakpoints
> are not hit, sometimes all threads seem to
> be hanging in the debugging case only.
>
> Is there a stable extension for the GDB/GDBSERVER
> providing thread debugging ?
>
> Thank you for help
>
> Steffen Rumler
>
> --
>
> --------------------------------------------------------------
>
> Steffen Rumler
> ICN ON PNE SB 4
> Siemens AG
> Hofmannstr. 51                 Email: Steffen.Rumler@icn.siemens.de
> D-81359 Munich                 Phone: +49 89 722-44061
> Germany                        Fax  : +49 89 722-36703
>
> --------------------------------------------------------------
>

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

  reply	other threads:[~2002-06-06 15: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 [this message]
2002-06-06 15:43   ` Rick Hunnicutt
2002-06-06 15:57     ` Mark Hatle
2002-06-06 16:14       ` Mark Hatle
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=3CFF7C68.C6151B82@mvista.com \
    --to=fray@mvista.com \
    --cc=Steffen.Rumler@icn.siemens.de \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).