Date: Wed, 12 May 1999 09:08:45 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: John Birrell <jb@cimlogic.com.au> Cc: current@freebsd.org Subject: Re: Debugging uthreads Message-ID: <Pine.BSF.4.05.9905120906500.385-100000@herring.nlsystems.com> In-Reply-To: <199905120753.RAA25621@cimlogic.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 May 1999, John Birrell wrote: > Doug Rabson wrote: > > I've put an initial version of my hack for debugging FreeBSD user threads > > with gdb up on http://www.freebsd.org/~dfr/uthread.diff. Comments would be > > appreciated. > > Is the uniqueid really necessary when the address of the thread structure > is already unique within the process address space? After all, that's > what the thread ID is (a pointer to the malloc'd memory). > > I have the feeling that there needs to be some way to discover if the > version of gdb being used is compatible with the version of libc_r that > the program is linked against. Otherwise we end up with a similar > problem to the all too familiar "struct proc size mismatch". 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. 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'. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 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?Pine.BSF.4.05.9905120906500.385-100000>