From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18310 invoked by alias); 19 Dec 2009 06:02:21 -0000 Received: (qmail 18302 invoked by uid 22791); 19 Dec 2009 06:02:20 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 19 Dec 2009 06:02:16 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id AED562BABFF; Sat, 19 Dec 2009 01:02:14 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id U5Q9+qSnQ4KL; Sat, 19 Dec 2009 01:02:14 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 3E1E52BABE6; Sat, 19 Dec 2009 01:02:14 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id D1899F58CC; Sat, 19 Dec 2009 07:02:01 +0100 (CET) Date: Sat, 19 Dec 2009 06:02:00 -0000 From: Joel Brobecker To: Perry Smith Cc: gdb@sourceware.org Subject: Re: gdb 6.8 on AIX (threads) Message-ID: <20091219060201.GF2804@adacore.com> References: <9EDDF928-9E32-4D49-A07F-EFEB3E6C93A9@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9EDDF928-9E32-4D49-A07F-EFEB3E6C93A9@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-12/txt/msg00125.txt.bz2 > Are there special configure options I needed? I don't see any. I > can put a break point in pthread_create and it stops there but > later, gdb still has no knowledge of the multiple threads. There is no special configure option. Thread support on AIX is based on libpthdebug, so perhaps this library is missing on your system. Or maybe you're missing the associated system headers. Alternatively, it could be a bug. If the thread module is built in, "set debug aix-thread" should turn traces on and help understanding what's going on. -- Joel