Re: Disabling lin-thread.c module

[Michael Snyder <msnyder at cygnus dot com>]

Mark Kettenis wrote:
> 
>    Date: Tue, 11 Apr 2000 07:16:40 -0400 (EDT)
>    From: Eli Zaretskii <eliz@delorie.com>
> 
>    I suggest option 3, but I also suggest to activate that autoconf test
>    and the entire feature only if the package is configured with
>    --enable-thread-db.  I think this is the right approach for an
>    experimental/dangerous feature which wasn't tested well enough.
> 
> Well, the alternative to the libthread_db assisted threads debugging
> code isn't that much better tested.  In both cases, the
> threads-related tests in the testsuite are passed.  I haven't seen any
> evidence of people doing more thread-related testing with gdb
> snapshots on Linux/i386.
> 
> Anyway, the --enable-thread-db option is completely orthogonal to the
> autoconf test.  I'd really like to see the libthread_db assisted code
> being used, otherwise we'll never learn about problems with it.
> Looks like Michael Snyder feels the same way. 

Moreover, we HAVE to start using it, because the older method
simply isn't going to continue working indefinitely, as LIBC
development moves forward.  The thread-db method was developed
for a reason: it helps to separate GDB from dependancy on 
knowledge of the internal details of implementation in libthread.