From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26112 invoked by alias); 18 Jun 2014 08:14:48 -0000 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 Received: (qmail 25988 invoked by uid 89); 18 Jun 2014 08:14:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_20,HELO_DYNAMIC_IPADDR,RDNS_DYNAMIC autolearn=no version=3.3.2 X-HELO: lvps176-28-13-145.dedicated.hosteurope.de Received: from lvps176-28-13-145.dedicated.hosteurope.de (HELO lvps176-28-13-145.dedicated.hosteurope.de) (176.28.13.145) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 18 Jun 2014 08:14:45 +0000 Received: from dabox.localnet (unknown [62.159.134.147]) by lvps176-28-13-145.dedicated.hosteurope.de (Postfix) with ESMTPSA id 9E6211BF5C001 for ; Wed, 18 Jun 2014 10:14:43 +0200 (CEST) From: Tim Sander To: gdb@sourceware.org Subject: Re: gdb single stepping takes ages Date: Wed, 18 Jun 2014 08:14:00 -0000 Message-ID: <2556774.80PXRilPAq@dabox> User-Agent: KMail/4.13 (Linux/3.13.0; KDE/4.13.0; x86_64; ; ) In-Reply-To: <11141246.9lllTVUqLL@dabox> References: <11141246.9lllTVUqLL@dabox> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-IsSubscribed: yes X-SW-Source: 2014-06/txt/msg00045.txt.bz2 Hi > I am currently using openocd as a gdbserver backend for debugging an > embedded target with gdb 7.7. When i want to step over a single line with > -exec-next: > > for(int a=0; a<1000000;a++){ }; > > the time taken for the step is linear to the maximum count number and takes > in my setup about 1 second for one increment of a. Setting a temp > breakpoint in the next line and continuing works much faster. > > So is there a way improve the stepping speed in such situations? > > Best regards > Tim Just after sending the mail recognized that the thread: "Remote Debugging with NEXT Command" touches a similar (the same?) issue. A solution mentioned was range checking. But in the openocd case it seems already enabled: show range-stepping Debugger's willingness to use range stepping is on. Best regards Tim