From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20335 invoked by alias); 14 Jan 2005 19:56:40 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 20208 invoked from network); 14 Jan 2005 19:56:33 -0000 Received: from unknown (HELO sj-iport-3.cisco.com) (171.71.176.72) by sourceware.org with SMTP; 14 Jan 2005 19:56:33 -0000 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 14 Jan 2005 13:03:10 +0000 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j0EJuTjw006402; Fri, 14 Jan 2005 11:56:30 -0800 (PST) Received: from dhcp-161-44-128-90.cisco.com (dhcp-161-44-128-90.cisco.com [161.44.128.90]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AOI61968; Fri, 14 Jan 2005 14:56:28 -0500 (EST) Subject: Re: showing the gdb commands executed by insight ? From: Jim Sullivan To: Keith Seitz Cc: "insight@sources.redhat.com" In-Reply-To: <1105722709.2746.8.camel@lindt.uglyboxes.com> References: <1105720744.5197.13.camel@fr-f1-c1-clnx> <1105722709.2746.8.camel@lindt.uglyboxes.com> Content-Type: text/plain Message-Id: <1105732588.5197.51.camel@fr-f1-c1-clnx> Mime-Version: 1.0 Date: Fri, 14 Jan 2005 19:56:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2005-q1/txt/msg00012.txt.bz2 Hi Keith, Here is an overview of my environment and the problem I am trying to solve. I am using a remote target. For debugging I typically 1. startup insight with the symbol file in the same directory. 2. set the target setting to remote serial, or remote tcp ...etc. 3. connect to the target All this works great. I can also disassem code after step 1 above, which implies that I do not have to be connected to the target to read the code. I would guess that insight looks at the symbol file, and object file to dump this information. Now if I wanted to do the same thing using GDB. I.e. disassem the code without connecting to the target I would think that I need only provide a symbol file and the location of the source, however your previous response implies it is more involved that this. more comments below. On Fri, 2005-01-14 at 12:11, Keith Seitz wrote: > On Fri, 2005-01-14 at 08:39, Jim Sullivan wrote: > > If I run insight and give it a symbol file > > I can disassemble the code and it works correctly. > > Sometimes. Can you explain ? > If you're using a remote target, I'll bet it appears to work because > insight always disassembles from the image file (as I recall). Gdb, on > the other hand, will disassemble from memory, so if you haven't loaded > an image onto your target, you're going to get gibberish. This would seem to explain it, but using set trust-readonly-sections did not solve the problem. thanks, Jim