From owner-freebsd-current Wed May 12 7:15:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 8EC8915CD1 for ; Wed, 12 May 1999 07:15:39 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id PAA00580; Wed, 12 May 1999 15:15:25 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 12 May 1999 15:15:24 +0100 (BST) From: Doug Rabson To: Daniel Eischen Cc: jb@cimlogic.com.au, current@FreeBSD.ORG Subject: Re: Debugging uthreads In-Reply-To: <199905121035.GAA10411@pcnet1.pcnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 May 1999, Daniel Eischen wrote: > 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. GDB's needs are rather simple. It needs to know the current thread, be able to enumerate all threads, and access the saved register set of a non-current thread. I don't want to over-engineer the thing given that writing the gdb side of things was actually pretty simple. -- 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