From owner-freebsd-current Wed May 12 1:55:49 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 BEF5A1503E for ; Wed, 12 May 1999 01:55:44 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id TAA25926; Wed, 12 May 1999 19:07:01 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905120907.TAA25926@cimlogic.com.au> Subject: Re: Debugging uthreads In-Reply-To: from Doug Rabson at "May 12, 1999 9:48:43 am" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 12 May 1999 19:07:01 +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: > That would work. I think I only need uniqueid, sig_saved, > saved_sigcontext, saved_jmpbuf, state and nxt. If those guys were lumped > up at the start of struct pthread (possibly in another struct so that gdb > doesn't need to know sizeof(struct pthread)) and marked appropriately then > the debugger interface would be quite stable. I'd be inclined to add the magic number too, because it gives a hint as to whether the structure refers to a valid thread. If the thread is destroyed, the magic number is trashed. I think it is worth adding a new header file defining such a structure. -- 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