All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Kalpesh Jasapara <kjasapara@yahoo.com>
Cc: gdb@sources.redhat.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: GDB server and threaded application
Date: Tue, 25 Mar 2003 23:05:34 -0500	[thread overview]
Message-ID: <20030326040533.GA26741@nevyn.them.org> (raw)
In-Reply-To: <20030326035830.20755.qmail@web14601.mail.yahoo.com>


On Tue, Mar 25, 2003 at 07:58:30PM -0800, Kalpesh Jasapara wrote:
> Hello,
>
> I am having a problem with remote gdb debugging
> using gdbserver to work with multi threads.
> The command "info threads" shows only one thread.
>
> I am using glibc 2.1.3, powerpc-linux-gdb 5.3,
> powerpc-linux-gcc 2.9.5
>
> Observed that qfThreadInfo packet response contains
> only
> one thread, not a list of all the threads in our
> application.
>
> How does the all_threads list get populated with the
> other
> threads?
>
> Is this feature supported with the versions that we
> are using?

I recommend you search the archives for this mailing list.  I've
still not written a good FAQ about this but I've answered the question
five or six times.

In short, probably your target libraries are not properly available to
the host GDB.

--
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

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

  reply	other threads:[~2003-03-26  4:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26  3:58 GDB server and threaded application Kalpesh Jasapara
2003-03-26  4:05 ` Daniel Jacobowitz [this message]
2003-03-26  5:39 ` Vladimir Gurevich
2003-03-26 13:41   ` Daniel Jacobowitz
2003-03-26 16:13     ` Wolfgang Denk
2003-03-27  0:00     ` Kalpesh Jasapara
2003-03-27  1:55       ` 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=20030326040533.GA26741@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=kjasapara@yahoo.com \
    --cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.