From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28083 invoked by alias); 5 Oct 2011 17:23:54 -0000 Received: (qmail 28075 invoked by uid 22791); 5 Oct 2011 17:23:53 -0000 X-SWARE-Spam-Status: No, hits=-7.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 05 Oct 2011 17:23:33 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p95HNTMw020386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Oct 2011 13:23:29 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p95HNSQ0007140; Wed, 5 Oct 2011 13:23:28 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p95HNQwI000770; Wed, 5 Oct 2011 13:23:27 -0400 From: Tom Tromey To: Josh Watt Cc: Pedro Alves , gdb@sourceware.org Subject: Re: Thread Specific Breakpoints in Remote Targets References: <201108311909.22045.pedro@codesourcery.com> <201108311942.00429.pedro@codesourcery.com> Date: Wed, 05 Oct 2011 17:23:00 -0000 In-Reply-To: (Josh Watt's message of "Thu, 1 Sep 2011 10:33:48 -0500") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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-10/txt/msg00012.txt.bz2 >>>>> "Josh" == Josh Watt writes: [ thread-specific breakpoints on the target ] Josh> Unless I'm missing something, I don't believe this would be too Josh> difficult to implement. Most of the code would live in remote.c and Josh> would require a new packet for handling thread breakpoints. I didn't see a response to this. Josh> Would something like this be OK, or did you have something else in mind? Josh> vThreadBreak;addr;kind;thread-id Josh> The only other question I currently have is how should the thread id Josh> be communicated to remote.c? Should the global inferior_ptid be used, Josh> or would we add another member to the struct bp_target_info that Josh> contains the thread ID? I don't know the details of the remote protocol, but yes, something like this would be good to have. On the gdb side, I would say adding a field to bp_target_info would be much better than a global. Tom