From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4041 invoked by alias); 9 Apr 2010 13:43:53 -0000 Received: (qmail 4022 invoked by uid 22791); 9 Apr 2010 13:43:52 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=BAYES_00,TW_OC,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 09 Apr 2010 13:43:47 +0000 Received: (qmail 25663 invoked from network); 9 Apr 2010 13:43:45 -0000 Received: from unknown (HELO caradoc.them.org) (dan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 9 Apr 2010 13:43:45 -0000 Date: Fri, 09 Apr 2010 13:43:00 -0000 From: Daniel Jacobowitz To: PILLON Julien Cc: Paul Koning , "gdb@sourceware.org" Subject: Re: RE : User level threads debugging with GDB Message-ID: <20100409134324.GA16597@caradoc.them.org> Mail-Followup-To: PILLON Julien , Paul Koning , "gdb@sourceware.org" References: <06A7AD4E92172446ADDEB44F8A5D5C101CA8246BEE@ARE01.alyotech.fr> <06A7AD4E92172446ADDEB44F8A5D5C101CA8246BF0@ARE01.alyotech.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <06A7AD4E92172446ADDEB44F8A5D5C101CA8246BF0@ARE01.alyotech.fr> 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: 2010-04/txt/msg00034.txt.bz2 On Fri, Apr 09, 2010 at 03:04:28PM +0200, PILLON Julien wrote: > Thank you for your answer. > The fact is that I don't want to make big modification to GDB... So I think I'll go on implementing a libthread_db (with this method, it will be compatible with future (and previous ?) versions of GDB ) This is not likely to work. Linux thread debugging uses a little bit of the libthread_db but also knows a great deal about native OS threads. There is also some libthread_db code for Solaris, but it's tied together with procfs support. There is no generic libthread_db layer. -- Daniel Jacobowitz CodeSourcery