From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31027 invoked by alias); 21 Jan 2011 23:06:22 -0000 Received: (qmail 31019 invoked by uid 22791); 21 Jan 2011 23:06:21 -0000 X-SWARE-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,BAYES_20,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mailgw.tensilica.com (HELO mailgw.tensilica.com) (65.119.96.134) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 21 Jan 2011 23:06:08 +0000 Received: from localhost (unknown [127.0.0.1]) by mailgw.tensilica.com (Postfix) with ESMTP id C4EFD1160924 for ; Fri, 21 Jan 2011 23:06:06 +0000 (UTC) Received: from mailgw.tensilica.com ([127.0.0.1]) by localhost (mailgw.tensilica.com [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 15349-04 for ; Fri, 21 Jan 2011 15:06:06 -0800 (PST) Received: from mail.tensilica.com (mail.tensilica.com [192.168.15.138]) by mailgw.tensilica.com (Postfix) with ESMTP id A15621160922 for ; Fri, 21 Jan 2011 15:05:49 -0800 (PST) Received: from [192.168.11.68] (192.168.11.68) by mail.tensilica.com (192.168.15.138) with Microsoft SMTP Server id 8.2.254.0; Fri, 21 Jan 2011 15:05:50 -0800 Message-ID: <4D3A114D.7010301@tensilica.com> Date: Sat, 22 Jan 2011 15:06:00 -0000 From: Maxim Grigoriev User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10 MIME-Version: 1.0 To: "gdb-patches@sourceware.org" , Marc Gauthier Subject: Faster stepping amidst breakpoints Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-01/txt/msg00450.txt.bz2 Hello GDB community, Has anyone tried to optimize the GDB protocol by letting the remote agent plant and unplant breakpoints when the target resumes and stops, rather than having GDB do it over the wire with round-trip latency on every single breakpoint plant& unplant request? Certain GDB operations involve a lot of single-stepping, which can be really slow on certain targets (especially embedded targets) because of that latency. In principle, GDB can query the remote agent to decide whether to apply this optimization. And the remote agent must be careful not to plant any breakpoint at the current PC when single-stepping. There are likely other considerations, but at a glance, it seems doable. So am curious whether there's any particular reason it wasn't done (that we could see). Thanks, -- Maxim