From owner-freebsd-current@FreeBSD.ORG Fri Feb 6 11:08:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B9F516A4CE for ; Fri, 6 Feb 2004 11:08:03 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A5F943D31 for ; Fri, 6 Feb 2004 11:08:02 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i16J7sfo018941; Fri, 6 Feb 2004 14:07:54 -0500 (EST) Date: Fri, 6 Feb 2004 14:07:54 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sean McNeil In-Reply-To: <1076093709.36910.3.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: gdb understanding kse? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2004 19:08:03 -0000 On Fri, 6 Feb 2004, Sean McNeil wrote: > I was looking at the same python issue everyone else had and I noticed > that people were able to determine it was in sem_destroy. I tried to > attach gdb to the process, but threads recognized for me. Is this > working? I read at one time it was going to go in eventually. > > How does one trace threads if kse isn't supported in gdb? It's being worked on and should be there for 5.3-release. There are already preliminary patches for it, but I suspect it won't hit the tree in a usable form until GDB 6.1 (or whatever) is imported. -- Dan Eischen