From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14658 invoked by alias); 15 May 2013 08:27:22 -0000 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 Received: (qmail 14588 invoked by uid 89); 15 May 2013 08:27:22 -0000 X-Spam-SWARE-Status: No, score=-4.6 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL autolearn=ham version=3.3.1 Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 15 May 2013 08:27:21 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1UcX3O-0000Yr-6M from Yao_Qi@mentor.com ; Wed, 15 May 2013 01:27:18 -0700 Received: from SVR-ORW-FEM-05.mgc.mentorg.com ([147.34.97.43]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 15 May 2013 01:27:17 -0700 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-05.mgc.mentorg.com (147.34.97.43) with Microsoft SMTP Server id 14.2.247.3; Wed, 15 May 2013 01:27:17 -0700 Message-ID: <519346F0.1030507@codesourcery.com> Date: Wed, 15 May 2013 08:27:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Pedro Alves CC: Subject: Re: [PATCH 6/7] range stepping: test case References: <1363006291-13334-1-git-send-email-yao@codesourcery.com> <1363006291-13334-7-git-send-email-yao@codesourcery.com> <51928327.5080803@redhat.com> In-Reply-To: <51928327.5080803@redhat.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2013-05/txt/msg00508.txt.bz2 On 05/15/2013 02:32 AM, Pedro Alves wrote: > I prefer this over the convenience variable hack. If we ever > make range stepping work on a target !remote, we can switch to > look at "set debug infrun 1" output or some new "set debug range-step" > output. I didn't understand your stated reason in v2 for > switching away from this. If it was that expect buffer > overflows, v3 has a tweak that likely fixes it. In our tests, when running tests with a problematic stub supporting range stepping, the range stepping of the stub falls back to the single stepping. This will generate a huge number of rsp packets, and the gdb.log will blow up to several giga-byte. We use convince variable to avoid this problem. On the other hand, I don't think it is a good idea to peek the GDB internal states by checking some rsp packets and personally I prefer the way that GDB is able to expose some internal states by some means (command "maint" and convince variables, for example). -- Yao (齐尧)