Re: expected behavior of GNU/Linux gcore and corefiles

Andrew Cagney
2003-03-02T20:03:01Z

>>
>> If that position means precluding certain native-only functionality?
>
>
> Not exactly; if that native-only functionality precludes keeping what
> we have now for non-thread_db setups and extending it.

> For instance, I
> think we should always be able to print LWP state (assuming a 1-1
> mapping when we have no thread_db to ask for more information). And I
> think we should add support for TLS based only on LWPs, since it's not
> dependent on the thread manager. If we can't "info mutex" on a cross
> corefile, well, that's the same as now.

To draw this back to the original post. What of a native GDB loading
libthread-db over a core file to determine thread IDs and TLS?

Andrew