From owner-freebsd-threads@FreeBSD.ORG Sat Mar 27 16:07:35 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C28416A4CE for ; Sat, 27 Mar 2004 16:07:35 -0800 (PST) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8BBC43D4C for ; Sat, 27 Mar 2004 16:07:34 -0800 (PST) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-216-100-132-94.dsl.snfc21.pacbell.net [216.100.132.94])i2S07RGa122534; Sat, 27 Mar 2004 19:07:33 -0500 Message-ID: <406616D1.6090108@elischer.org> Date: Sat, 27 Mar 2004 16:05:37 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: Niall Douglas References: <406605CC.14911.CD2D006@localhost> In-Reply-To: <406605CC.14911.CD2D006@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-threads@freebsd.org Subject: Re: GDB 6.0 and FreeBSD threads X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Mar 2004 00:07:35 -0000 Niall Douglas wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I'm nearly finished porting my project to FreeBSD from Linux but I'm > getting a SIGSEGV at odd places in the code. Unfortunately my project > absolutely requires G++ v3.4 as the template support in v3.3 is not > up to par. Hence one has a problem debugging the executable with gdb > <6.0 (it works, but it's flaky). > > I tried compiling gdb 6.0 on FreeBSD and it compiles fine. > Unfortunately it appears to be missing thread support which is most > annoying. After searching around, I've discovered you guys patched > gdb 5.x with uthread.c. > > Here's my question - how much work would be required to getting the > 5.x uthread.c to work with gdb 6.0? Has somebody already done most of > the work (if so, can you supply me with a diff)? I don't need > fantastic support, just enough to help me find this bug (it's weird - > it's almost as though g++ is writing off the end of the stack ie; bad > code generation. Yet surely if that were the case, we'd have the same > SIGSEGV on Linux :( ). > > Any info much appreciated. > > Cheers, > Niall > David Xu is doing gdb support for the new threads code however it is for the gdb in teh system. I don;t know how different it wouldbe for 6.0 but you may end up needing to do some work on it yourself if you can get his patches. -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v