Date: Wed, 12 May 1999 06:35:31 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: eischen@vigrid.com, jb@cimlogic.com.au Cc: current@FreeBSD.ORG, dfr@nlsystems.com Subject: Re: Debugging uthreads Message-ID: <199905121035.GAA10411@pcnet1.pcnet.com>
index | next in thread | raw e-mail
John Birrell wrote: > Daniel Eischen wrote: > > Why don't we make a libc_r_db and provide the necessary interfaces to > > gdb from that instead of having gdb know about uthread internals? > > It would still mean that gdb would be linked to the uthread internals > which may not match the version of libc_r that the 3rd party program > was linked against. OK, but it still seems more appropriate to have uthread debugging internals known somewhere other than in GDB. It seems more obvious to have to modify libc_r_db when libc_r changes than to know to update the gdb sources. If threads had versioning information as well as trying to set certain attributes in stone, then libc_r_db could be made to be backwards compatible with older thread libraries. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the messagehelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905121035.GAA10411>