This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: Disabling lin-thread.c module
- To: Mark Kettenis <kettenis at wins dot uva dot nl>
- Subject: Re: Disabling lin-thread.c module
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Tue, 11 Apr 2000 07:16:40 -0400 (EDT)
- CC: gdb at sourceware dot cygnus dot com, msnyder at cygnus dot com
- References: <200004101237.OAA29849@landau.wins.uva.nl>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Since glibc-2.1.3 was released with a bogus definition for
> prfpregset_t (at least for Linux/i386[1]), we'll have to take some
> measures to make sure that GDB-5.0 will work with glibc-2.1.3.
>
> I see three possibilities:
>
> 1. Disable the lin-thread.c module by default, and provide a switch
> --enable-thread-db to enable the module, such that people can build
> the module if the headers have been fixed (for example when
> glibc-2.1.4 has been installed).
>
> 2. Provide the same switch, but use an autoconf test to check whether
> the prfpregset_t type is broken, and enable the module based on the
> result of that test.
>
> 3. Use an autoconf test to check whether the prfpregset_t type is
> broken, and let GDB work around it.
>
> I'm inclined to implement option 3, since that means that the
> lin-thread.c code will be somewhat more thoroughly tested, but there
> may be some drawbacks:
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.