This is the mail archive of the gdb@sourceware.cygnus.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Disabling lin-thread.c module


On Tue, Apr 11, 2000 at 01:48:46PM +0200, 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.  But if there are more
> people who think disabling the code by default and adding
> --enable-thread-db is a good idea, I'll be happy to add it.

People are using gdb for real work. They shouldn't second guess
about gdb. I vote for disable libthread_db by default for 5.0
and turn it on in CVS. People who use the public release won't
get libthread_db by default. But they will test libthread_db if
they use CVS or snapshot.


H.J.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]