From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5302 invoked by alias); 21 May 2014 09:55:36 -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 5293 invoked by uid 89); 21 May 2014 09:55:35 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 21 May 2014 09:55:35 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s4L9tWTT026228 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 21 May 2014 05:55:32 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s4L9tUAx010151; Wed, 21 May 2014 05:55:30 -0400 Message-ID: <537C7811.7010607@redhat.com> Date: Wed, 21 May 2014 09:55:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Markus Metzger CC: gdb-patches@sourceware.org, Eli Zaretskii Subject: Re: [PATCH v3 1/3] btrace: control memory access during replay References: <1400655682-4014-1-git-send-email-markus.t.metzger@intel.com> In-Reply-To: <1400655682-4014-1-git-send-email-markus.t.metzger@intel.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-05/txt/msg00466.txt.bz2 On 05/21/2014 08:01 AM, Markus Metzger wrote: > The btrace record target does not trace data. We therefore do not allow > accessing read-write memory during replay. > > In some cases, this might be useful to advanced users, though, who we assume > to know what they are doing. > > Add a set|show command pair to turn this memory access restriction off. > Code bits are OK. -- Pedro Alves