From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11095 invoked by alias); 1 May 2013 03:36:19 -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 11085 invoked by uid 89); 1 May 2013 03:36:18 -0000 X-Spam-SWARE-Status: No, score=-5.1 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.1 Received: from mail-ve0-f181.google.com (HELO mail-ve0-f181.google.com) (209.85.128.181) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 01 May 2013 03:35:46 +0000 Received: by mail-ve0-f181.google.com with SMTP id d10so989232vea.12 for ; Tue, 30 Apr 2013 20:35:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=ayeW0EryWy11bpdwrSVfsCe4HtwWYwQSAdPZDz6Jf74=; b=dcYSLrgvYImKpBfY1haooBHaPcx5QgP5GzzDdbpZM7p9oyv7P8f/ZFeZOMYD/uYhSd A9JAy3kU5uJ00UkMvPaUhfH2GSgyq8uUw9BQSivu8PT63MnlYFKc/ejlJTVz8zIUgO8S IpkkATCqBJP+/RNInvhyEaoPcSnj7pACMQKMfN6brHqKFQ3hMlsc/lnZd4bNV23tnDiT yESruh4zs7jpF/Syz/mnsOGWFVUKZFuX+aTfaJXKuYycfXDpIa5tgq8cUS74Y1MwN175 OEhyw04YGE2NpeKZVklBfTftXr2FIqV7DBJYZINe7Z58Jl/J6dBx6/MTgNS+JpNsuIJF 19LA== MIME-Version: 1.0 X-Received: by 10.58.198.79 with SMTP id ja15mr395936vec.15.1367379345118; Tue, 30 Apr 2013 20:35:45 -0700 (PDT) Received: by 10.220.173.7 with HTTP; Tue, 30 Apr 2013 20:35:44 -0700 (PDT) In-Reply-To: <51778299.40402@indel.ch> References: <517516D8.6010604@indel.ch> <5177425D.7080901@codesourcery.com> <51778299.40402@indel.ch> Date: Wed, 01 May 2013 03:36:00 -0000 Message-ID: Subject: Re: Unneeded displaced single stepping causes issues: Performance drop and range stepping killer From: Doug Evans To: Raphael Zulliger Cc: Yao Qi , gdb Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlwSVHLeQ50Qfnn3gCKIAeosp+iX1+Gb4kOAxJVYnjaHNuNvSpltyPdJfLtUaMS68/Gng9fwPTcS05nerZDez6bgPQ13zGedofsqV+UpEHifXvSM3XOes++mCER/fqmcjX2lTxSFLImeNAbcbqmLWINsapnZL0FZbYv85wWAEcOQ0G+z4lRDDzSjZDBQ+MiU8k8L+I5 X-SW-Source: 2013-05/txt/msg00001.txt.bz2 On Tue, Apr 23, 2013 at 11:58 PM, Raphael Zulliger wrote: > - There's something I hope we could improve (but I haven't looked > into the code yet): When GDB receives a stop reply, it issues many "memory > reads". Sometimes it read consecutive memory by multiple RSP packages. > Sometime it even reads the same memory region twice. It's unfortunate that gdb's remote caching support doesn't work better "out of the box".