From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30639 invoked by alias); 16 Aug 2004 19:30:12 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 30618 invoked from network); 16 Aug 2004 19:30:11 -0000 Received: from unknown (HELO fencepost.gnu.org) (199.232.76.164) by sourceware.org with SMTP; 16 Aug 2004 19:30:11 -0000 Received: from eliz by fencepost.gnu.org with local (Exim 4.34) id 1BwnBK-0001to-T2; Mon, 16 Aug 2004 15:30:10 -0400 From: Eli Zaretskii To: Fabian Cenedese CC: gdb@sources.redhat.com In-reply-to: <5.2.0.9.1.20040816154657.01ce05d0@NT_SERVER> (message from Fabian Cenedese on Mon, 16 Aug 2004 16:20:39 +0200) Subject: Re: Thread-specific breakpoints Reply-to: Eli Zaretskii References: <5.2.0.9.1.20040816090919.01cefeb0@NT_SERVER> <5.2.0.9.1.20040816090919.01cefeb0@NT_SERVER> <5.2.0.9.1.20040816154657.01ce05d0@NT_SERVER> Message-Id: Date: Mon, 16 Aug 2004 19:30:00 -0000 X-SW-Source: 2004-08/txt/msg00221.txt.bz2 > Date: Mon, 16 Aug 2004 16:20:39 +0200 > From: Fabian Cenedese > > > >The closest GDB comes is "break thread ". > > Yes, that's along the lines I was thinking. And after intense looking I even > found it in the manual. I missed it the first time as the break command > is explained in 5.1.1 whereas break thread by itself > is in 5.4. The `i' (Info-index) command is your friend. In an Info browser, type "i thread" and you will be presented with a list of thread-related index entries that are recorded in the manual. Through sheer luck (or maybe something else ;-), the very first entry is exactly what you wanted.