Re: (linux/threads) Interesting side-effect of "auto-solib-add 0"

[Joel Brobecker <brobecker@adacore.com>]

> You've missed the pertinent fact here.  We're not waiting for
> libpthread.so to be loaded just for kicks!  The only way libthread_db
> can operate is by querying back through GDB for the locations of
> symbols in the thread library.  If we don't load that objfile, then
> it can't initialize.

It's really strange. I put traces everywhere inside linux-thread-db
so that if there was any callbacks called during the detection,
I would see them. As you can see, I'm not very familiar with how
this library works. Do you know where the callbacks are in the
debugger code? I've been trying to find a document that explains
how the pthread_db library works, is there one?

> > The only difference I can see between the two runs is that symbols
> > are read in one case, and not read in the other case. Is libthread_db.so
> > dependent on having the symbol table being loaded or something of that
> > sort?
> 
> Yes.  Don't load libpthread, won't get threads.

Sounds fair enough to me.

Eli, everyone,

Would it be something worth documenting somewhere in the manual?
I could probably write a small paragraph somewhere after the description
of the auto-solib-add setting.

Thanks!
-- 
Joel