From owner-freebsd-current Wed May 12 1:30:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id D472414C12 for ; Wed, 12 May 1999 01:30:51 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id SAA25827; Wed, 12 May 1999 18:42:11 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905120842.SAA25827@cimlogic.com.au> Subject: Re: Debugging uthreads In-Reply-To: from Doug Rabson at "May 12, 1999 9:28: 0 am" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 12 May 1999 18:42:11 +1000 (EST) Cc: jb@cimlogic.com.au, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > Other gdb thread debugging systems tend to export a set of variables from > the thread library which describe the important offsets in the thread > structure e.g. _debug_pthread_status_offset, _debug_pthread_foo_offset > etc. > > If you think there will be a real problem, I could do this I guess. Maybe we should just isolate the things that gdb is allowed to look at and document them as "cast in stone". -- 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