Re: regarding transparent data ranges (in tracepoint support)

[Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>]

Newman, Mark (N-Superior Technical Resource Inc) wrote:

>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).
>  
>

I would also leave the option upto the user to say whether he wants to 
actually collect the data from the transparent
regions.
what say others?
cheers
Ramana

>                                               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
>>
>>    
>>