From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1267 invoked by alias); 19 Nov 2003 18:55:38 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 1260 invoked from network); 19 Nov 2003 18:55:37 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 19 Nov 2003 18:55:37 -0000 Received: from drow by nevyn.them.org with local (Exim 4.24 #1 (Debian)) id 1AMXUF-0002hJ-Gw; Wed, 19 Nov 2003 13:55:35 -0500 Date: Wed, 19 Nov 2003 18:55:00 -0000 From: Daniel Jacobowitz To: ankit thukral Cc: Jim Blandy , gdb@sources.redhat.com Subject: Re: regarding transparent data ranges (in tracepoint support) Message-ID: <20031119185534.GA5976@nevyn.them.org> Mail-Followup-To: ankit thukral , Jim Blandy , gdb@sources.redhat.com References: <20031119162537.27442.qmail@web60108.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031119162537.27442.qmail@web60108.mail.yahoo.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-11/txt/msg00153.txt.bz2 On Wed, Nov 19, 2003 at 08:25:37AM -0800, ankit thukral wrote: > > --- Jim Blandy wrote: > > > > ankit thukral writes: > > > > > hi all, > > > i read about the transparent data ranges and > > > learned that data in these ranges are not supposed > > to > > > be collected by the remote stub since they belong > > to > > > read-only segment of the debuggee.my problem is : > > a > > > TSTART would start the debuggee and it may so > > happen > > > that the debuggee finishes executing.at this > > point,if > > > the GDB requests for some data in the transparent > > data > > > range,then how can the remote stub provide it with > > one > > > since the debuggee has exited ? > > > > If the target is a gdbserver, then it would need to > > read the bytes > > from the executable file. This is easy to do with > > BFD, but if I > > remember right, gdbserver doesn't use BFD at the > > moment; not sure how > > to get around that. > > > > If the target is an embedded system, then presumably > > the transparent > > data ranges correspond to ROM regions, so the data > > is still there. > > > > how about setting a (internal) breakpoint in the > debuggee which would prevent it from exiting even > though it has finished executing main(),and then > entertain GDB requests for the transparent (or > read-only) memory regions by reading from the memory > of the debuggee??? That would work (but be wasteful). At least on Linux, you could read /proc/pid/maps to find what ranges correspond to where in what file, and save that information. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer