From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19845 invoked by alias); 31 Aug 2011 18:30:03 -0000 Received: (qmail 19769 invoked by uid 22791); 31 Aug 2011 18:30:01 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-ey0-f169.google.com (HELO mail-ey0-f169.google.com) (209.85.215.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 31 Aug 2011 18:29:45 +0000 Received: by eye22 with SMTP id 22so1241899eye.0 for ; Wed, 31 Aug 2011 11:29:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.55.219 with SMTP id v27mr438758fag.2.1314815384362; Wed, 31 Aug 2011 11:29:44 -0700 (PDT) Received: by 10.223.118.144 with HTTP; Wed, 31 Aug 2011 11:29:44 -0700 (PDT) In-Reply-To: <201108311909.22045.pedro@codesourcery.com> References: <201108311909.22045.pedro@codesourcery.com> Date: Wed, 31 Aug 2011 18:30:00 -0000 Message-ID: Subject: Re: Thread Specific Breakpoints in Remote Targets From: Josh Watt To: Pedro Alves Cc: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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/msg00135.txt.bz2 >> It sounds like you are making breakpoints on the target thread-specific >> based on the current thread. =A0But 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? -- ~JPEW