From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5313 invoked by alias); 22 Sep 2010 19:09:29 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 5301 invoked by uid 22791); 22 Sep 2010 19:09:28 -0000 X-SWARE-Spam-Status: No, hits=-6.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org From: Tom Tromey To: Oleg Nesterov Cc: archer@sourceware.org, utrace-devel@redhat.com Subject: Re: gdbstub initial code, v11 References: <20100922022226.GA27400@redhat.com> Date: Wed, 22 Sep 2010 19:09:00 -0000 In-Reply-To: <20100922022226.GA27400@redhat.com> (Oleg Nesterov's message of "Wed, 22 Sep 2010 04:22:26 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2010-q3/txt/msg00211.txt.bz2 Oleg> But what about features? What should I do next? all-stop, Oleg> thread-specific breakpoints (currently I have no idea what Oleg> this means), or what? I think it would be good to implement a feature that shows how this approach is an improvement over the current state of gdb+ptrace or gdb+gdbserver. Exactly what feature this should be... I don't know :-) I would imagine something performance-related. There was previously some discussion about some watchpoint-related thing, I forget the details of that. I don't think thread-specific breakpoints are exposed outside of gdb yet. If that is true, then implementing that would mean adding remote protocol features and also other stuff inside gdb. So, I would suggest not tackling this yet. Tom