From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30427 invoked by alias); 20 Nov 2007 12:17:06 -0000 Received: (qmail 30417 invoked by uid 22791); 20 Nov 2007 12:17:05 -0000 X-Spam-Check-By: sourceware.org Received: from bluesmobile.specifix.com (HELO bluesmobile.specifix.com) (216.129.118.140) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 20 Nov 2007 12:16:58 +0000 Received: from [127.0.0.1] (bluesmobile.specifix.com [216.129.118.140]) by bluesmobile.specifix.com (Postfix) with ESMTP id E77383C0CF; Tue, 20 Nov 2007 03:56:48 -0800 (PST) Subject: Re: It takes a long time to disassemble some instructions for remote target From: Michael Snyder To: Robert Bu Cc: gdb@sourceware.org In-Reply-To: References: Content-Type: text/plain Date: Tue, 20 Nov 2007 12:17:00 -0000 Message-Id: <1195560370.23780.17.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 (2.10.3-4.fc7) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 X-SW-Source: 2007-11/txt/msg00193.txt.bz2 On Tue, 2007-11-20 at 14:46 +0800, Robert Bu wrote: > > On Wed, 2007-11-14 at 16:39 +0800, Robert Bu wrote: > >> Hello all, > >> > >> When I try to disassemble a range of instructions, for example from > >> PC1 to PC2, GDB tries to fetch and disassemble the instructions one by > >> one. This may not be a problem for native debugging, or for remote > >> debugging with high connection speed. However, it takes some long time > >> for a not so fast serial connection, since GDB fetches one instruction > >> at a time, which results in a lot of 'm' packets. > >> Is that possible for GDB to fetch all instructions back for one time > >> with just one(maybe more than one, but now a lot of) 'm' packet, and > >> disassemble them locally one by one? > > > > My friend, I have just the thing you need! > > It slices! It dices! It prevents gdb from > > needlessly fetching memory from text sections! > > > > All ya gotta do is type "set trust-readonly"! > > And if ya don't trust me (but who am I kidding, > > EVERYBODY trusts a carny!), you can just type > > "help set trust-readonly" and read all about it > > yourself! > > > This option does not work in GDB 6.4. However it works in GDB 6.6. Quite > strange! Yes, it was broken for a while. Now it is fixed, and hopefully we will keep it fixed.