Re: Remote mutli-threaded debugging with large number of threads

On Mon, Jul 16, 2007 at 01:38:08PM +0200, m.sikorski0poczta.onet.pl wrote:
> After looking further into it and trying to narrow down
issue cause I found out that probably not number of threads
does matter here, but amount of debug information or binary
size.
> The improper case operated on binary of ~17MB (with
debug symbols) - after removing symbols from all app threads
except of one it seems to be working fine (binary size
reduced to ~7MB).
> 
> Does anyone have any comments/suggestions? Is there any
configuration change to support large binaries or is this
simply a bug in GDB?

It is extremely unlikely that this is it either.  It is
probably some
specific characteristic of the second application, e.g. a
confusing
bit of debug info.

-- 
Daniel Jacobowitz
CodeSourcery

Yes, I agree it has nothing to do with application size -
just confirmed that I can see correctly threads of 17 meg
binary. 
Interesting thing is that after running debug session on
first working application (one that problem never appeared),
then detaching and attaching to second one everything works
perfectly.

Gdbserver is restarted and attached to a second app. It
seems that it is a matter of configuration GDB keeps from
previous connection.
This is a kind of workaround for me, but still dont know
root cause. Any suggestions what I can look for in remote
debug logs?

Maciej Sikorski



Użytkownik Daniel Jacobowitz <drowfalse.org> napisał:
>
>It is extremely unlikely that this is it either.  It is
probably some
>specific characteristic of the second application, e.g.
a confusing
>bit of debug info.
>
>-- 
>Daniel Jacobowitz
>CodeSourcery
>