Re: gdb and dlopen

Andrew Cagney
2001-10-17T23:14:00Z

> Remember, ptid_get_pid() is the messenger. The real problem is
>> elsewhere. A bit like STREQ() in the symtab code.
>
>
> I don't understand what you mean by this. We certainly need to get at
> the actual PID everywhere PIDGET () is being used, regardless of
> whether it could be hoisted out of loops.

To give an example, instead of accessing multiple thread objects
simultaneously, GDB has a single global current thread state which it
swaps in and out (using memcpy() and invalidate all). As a consequence
GDB spends its time doing this song and dance where is constantly and
needlessly checks that the current single global thread is the correct
current single global thread.

enjoy,
Andrew