From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13344 invoked by alias); 31 Aug 2011 18:42:17 -0000 Received: (qmail 13336 invoked by uid 22791); 31 Aug 2011 18:42:17 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,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; Wed, 31 Aug 2011 18:42:03 +0000 Received: (qmail 22087 invoked from network); 31 Aug 2011 18:42:02 -0000 Received: from unknown (HELO scottsdale.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 31 Aug 2011 18:42:02 -0000 From: Pedro Alves To: Josh Watt Subject: Re: Thread Specific Breakpoints in Remote Targets Date: Wed, 31 Aug 2011 18:42:00 -0000 User-Agent: KMail/1.13.6 (Linux/2.6.38-11-generic; KDE/4.7.0; x86_64; ; ) Cc: gdb@sourceware.org References: <201108311909.22045.pedro@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201108311942.00429.pedro@codesourcery.com> 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: 2011-08/txt/msg00136.txt.bz2 On Wednesday 31 August 2011 19:29:44, Josh Watt wrote: > >> It sounds like you are making breakpoints on the target thread-specific > >> based on the current thread. But I thought we didn't (yet) have a way > >> to inform the target that a given breakpoint was thread-specific (but I > >> don't know this area extremely well -- if I'm wrong I'd like to know > >> about it). > > > > You're right, we don't. > > > >> I think it would be preferable to > >> implement real target support for thread-specific breakpoints. > > > > Very much. > > Is there a particular reason why the select thread packet (Hg) cannot > also control which thread a breakpoint is targeted for? There's that backwards compatibility thing. You'd have to come up with a way to get the current behavior of "breakpoint applies to all threads of this process". You'd need to add some new meaning to something like Hg0/HgPID.0, which is close, but that's not what it means today, so without other changes, you'd be left with the target not knowing what this particular gdb is trying to say (because you don't know whether the connecting gdb understands "thread specific" or not). -- Pedro Alves