From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21565 invoked by alias); 17 Nov 2003 17:26:29 -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 21553 invoked from network); 17 Nov 2003 17:26:28 -0000 Received: from unknown (HELO mailgw3a.lmco.com) (192.35.35.7) by sources.redhat.com with SMTP; 17 Nov 2003 17:26:28 -0000 Received: from emss04g01.ems.lmco.com ([166.17.13.122]) by mailgw3a.lmco.com (8.11.6p2/8.11.6) with ESMTP id hAHHQQd08732; Mon, 17 Nov 2003 12:26:27 -0500 (EST) Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.1-1X6 #30760) id <0HOI00101B42ZO@lmco.com>; Mon, 17 Nov 2003 12:26:26 -0500 (EST) Received: from EMSS04I00.us.lmco.com ([166.17.13.135]) by lmco.com (PMDF V6.1-1X6 #30760) with ESMTP id <0HOI00DYYB421M@lmco.com>; Mon, 17 Nov 2003 12:26:26 -0500 (EST) Received: from EMSS04M11.us.lmco.com ([144.219.10.27]) by EMSS04I00.us.lmco.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 17 Nov 2003 12:26:25 -0500 Date: Mon, 17 Nov 2003 17:26:00 -0000 From: "Newman, Mark (N-Superior Technical Resource Inc)" Subject: RE: regarding transparent data ranges (in tracepoint support) To: ankit thukral , gdb@sources.redhat.com Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 17 Nov 2003 17:26:25.0245 (UTC) FILETIME=[ED4758D0:01C3AD2F] X-SW-Source: 2003-11/txt/msg00129.txt.bz2 ankit - My feeling (i.e. imho) is that the engineer should be able to get at tracepointed data at any time. To me tracepointed data provides an historical "trail" of what occurred during the execution of the inferior. The engineer needs to be able to "see" that data while the inferior is running and after the inferior stops. When the operator specifies a time slice (via a tfind) then only the data collected should be available to that engineer. Anything else that he/she would see would be from a different time slice. I realize that transparent data should not change - but the engineer may be looking to see if it did change inappropriately. If the engineer wants to "see" that transparent data it should have been collected. (Which leaves open the question of whether or not an engineer should be able to collect transparent data). Mark Newman > -----Original Message----- > From: gdb-owner@sources.redhat.com > [mailto:gdb-owner@sources.redhat.com]On Behalf Of ankit thukral > Sent: Sunday, November 16, 2003 1:32 AM > To: gdb@sources.redhat.com > Subject: regarding transparent data ranges (in tracepoint support) > > > 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 ? > i think the debuggee needs to be stopped after > main() has finished .this may be achieved by setting > an internal breakpoint somewhere (i have no idea > where).or may be something else. > any ideas or suggestions?? > > > thanks in advance, > ankit. > > __________________________________ > Do you Yahoo!? > Protect your identity with Yahoo! Mail AddressGuard > http://antispam.yahoo.com/whatsnewfree >