From: Jim Blandy <jimb@codesourcery.com>
To: m.sikorski0@poczta.onet.pl
Cc: gdb@sourceware.org
Subject: Re: Remote mutli-threaded debugging with large number of threads
Date: Wed, 11 Jul 2007 19:15:00 -0000 [thread overview]
Message-ID: <m3r6nezr8m.fsf@codesourcery.com> (raw)
In-Reply-To: <Q14453297-7b364f6c234ad7b47650e260868e94a0@pmq4.test.onet.pl> (m.'s message of "Wed, 11 Jul 2007 10:27:22 +0200")
m.sikorski0@poczta.onet.pl writes:
> Hello,
> I faced recently strange issue using remote gdb debugging (cross i386-ppc). With ~60 threaded application debugging does not work well.
>
> Info threads returns incomplete information:
> (gdb) info threads
> 60 Thread 2150 0x00000000 in ?? ()
> 59 Thread 2151 0x00000000 in ?? ()
> 58 Thread 2152 0x00000000 in ?? ()
> 57 Thread 2153 0x00000000 in ?? ()
> 56 Thread 2155 0x00000000 in ?? ()
> 55 Thread 2156 0x00000000 in ?? ()
> 54 Thread 2157 0x00000000 in ?? ()
> ...
That is disappointing. Can you type 'set debug remote 1' and see what
information the stub is returning to GDB for these threads?
next prev parent reply other threads:[~2007-07-11 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 8:27 m.sikorski0
2007-07-11 19:15 ` Jim Blandy [this message]
2007-07-16 11:38 m.sikorski0
2007-07-16 11:49 ` m.sikorski0
2007-07-16 12:02 ` Daniel Jacobowitz
2007-07-16 15:44 m.sikorski0
2007-07-18 3:41 Maciej Sikorski
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=m3r6nezr8m.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=m.sikorski0@poczta.onet.pl \
/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