From owner-freebsd-threads@FreeBSD.ORG Sat Mar 27 14:52:30 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 D11B016A4CE for ; Sat, 27 Mar 2004 14:52:30 -0800 (PST) Received: from mail2.mail.iol.ie (mail2.mail.iol.ie [193.95.141.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18EDA43D41 for ; Sat, 27 Mar 2004 14:52:30 -0800 (PST) (envelope-from s_sourceforge@nedprod.com) Received: from dialup024.ts523.cwt.esat.net ([194.165.172.24] helo=kate) by mail2.mail.iol.ie with esmtp (Exim 3.36 #9) id 1B7MfE-0002Ql-00 for freebsd-threads@freebsd.org; Sat, 27 Mar 2004 22:52:28 +0000 From: "Niall Douglas" To: freebsd-threads@freebsd.org Date: Sat, 27 Mar 2004 22:53:00 -0000 MIME-Version: 1.0 Message-ID: <406605CC.14911.CD2D006@localhost> Priority: normal X-PM-Encryptor: IDWPGP-PM32, 4 X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: 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: Sat, 27 Mar 2004 22:52:30 -0000 -----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 -----BEGIN PGP SIGNATURE----- Version: idw's PGP-Frontend 4.9.6.1 / 9-2003 + PGP 8.0.2 iQA/AwUBQGYFzcEcvDLFGKbPEQJHlgCfY2KKaQOzPskaSQHegsIzMDmgR5IAnib6 AXyRMyuQgka/IvsjlI6dZS5w =b1Vq -----END PGP SIGNATURE-----