From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23338 invoked by alias); 17 Feb 2007 08:51:12 -0000 Received: (qmail 23328 invoked by uid 22791); 17 Feb 2007 08:51:11 -0000 X-Spam-Check-By: sourceware.org Received: from Unknown (HELO mail.hofr.at) (194.112.174.227) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 17 Feb 2007 08:51:06 +0000 Date: Sat, 17 Feb 2007 10:37:00 -0000 From: Nicholas Mc Guire To: David Highley cc: gdb@sourceware.org Subject: Re: Break in a thread but continue other threads In-Reply-To: <200702161602.l1GG2gpr014571@douglas.highley-recommended.com> Message-ID: References: <200702161602.l1GG2gpr014571@douglas.highley-recommended.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-IsSubscribed: yes 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: 2007-02/txt/msg00180.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Is it possible to put a break in one thread but continue all the other > threads? Our developers keep lamenting to me the inadequacies of the gdb > debugger in debugging our run time configured multi-threaded > applications. In several cases I can answer read the manual but in > others I know the persons diligence and capabilities. While ddd is ok it > would not be considered a great interface by any standard. I peronally > am not complaining as I do not use any of the integrated development > environments but I get plenty of input from the developer community; > 300+ on just one program. > One posible solution for this problem would be to use tracepoints - we have completed the first version of tracepoints for Linux (PPC,MIPS,X86) and it is available via cvs at: cvs -d :pserver:anoncvs@dslab.lzu.edu.cn:/home/cvs login password: anoncvs cvs -d :pserver:anoncvs@dslab.lzu.edu.cn:/home/cvs co tracepoints In the cvs you also can find a preliminary user manual - but this is still work in progress. Its also in ftp (cvs snapshot) at: ftp://dslab.lzu.edu.cn:/pub/gdb_tracepoints the monolitic patches for the current version are in: ftp://dslab.lzu.edu.cn:/pub/gdb_tracepoints/tracepoint-release/tracepoint-0.2 basically you only need that one patch file unless you are interested in the internals and want to join in (which we off course don't mind). Note though that there are some principle problems with ptrace based debugging (on Linux at least) as a thread that enteres via ptrace_stop are delayed until the next tick, which causes relatively large delays - this seems to be a Linux "bug" though which simply did not bother anybody as long as breakpoints are interactive only. hofrat -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFF1revnU7rXZKfY2oRAjeQAJ95uupGgnYxmGjyFKrinXxGSgcS9gCfUWyz u4KDAzlunXtyxaINJAhgrsg= =1v8L -----END PGP SIGNATURE-----