Date: Wed, 12 May 1999 18:27:03 +1000 (EST) From: John Birrell <jb@cimlogic.com.au> To: dfr@nlsystems.com (Doug Rabson) Cc: jb@cimlogic.com.au, current@freebsd.org Subject: Re: Debugging uthreads Message-ID: <199905120827.SAA25753@cimlogic.com.au> In-Reply-To: <Pine.BSF.4.05.9905120906500.385-100000@herring.nlsystems.com> from Doug Rabson at "May 12, 1999 9: 8:45 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Rabson wrote: > I didn't want to use the address since it might cause confusion if a > thread was freed and then the memory was re-allocated to create a new > thread. Good reason. > I thought about the versioning but I don't think it will be a problem in > practice since both uthread and gdb will generally be built by a single > 'make world'. But libc_r isn't linked into anything during a 'make world'. It is only linked to 3rd party applications. So, although libc_r and gdb are in sync at the end of a 'make world', any statically linked applications will be out-of-sync (if an internal change has been made to libc_r). I'm not sure there is an easy solution to this. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905120827.SAA25753>