On Mon, 11 Feb 2002, Kip Macy wrote: > > > > There's no reason freebsd-uthread.c has to be included in gdb. > > I think that there are instances when an individual wants to use the latest and > greatest version of GDB and still have thread support. Even if the threads > library does change, the objfile function should be able to take that into > account.
But the latest and greatest GDB (which should be a port) isn't likely to have a version of freebsd-uthread.c that works with the current libc_r or libpthread. We haven't even started the userland part of threadsNG so we have no idea what freebsd-uthread.c is going to look like. And when we do, expect a lot of changes to it. And just a day ago, I made a change to libc_r that requires (as yet uncommitted) mods to freebsd-uthread.c. IMHO, it doesn't make sense to include support for our threads into gdb just yet. If you import a recent gdb into current, then we already have a freebsd-uthread.c that can be modified as our threads library changes. If you make gdb a port, support for threads is going to be different depending on what version or release of FreeBSD you build for. -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
