This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: regarding transparent data ranges (in tracepoint support)
- From: ankit thukral <ankit_plug at yahoo dot com>
- To: "Newman, Mark \(N-Superior Technical Resource Inc\)" <mark dot newman at lmco dot com>, Daniel Jacobowitz <drow at mvista dot com>
- Cc: ankit thukral <ankit_plug at yahoo dot com>, Jim Blandy <jimb at redhat dot com>, gdb at sources dot redhat dot com
- Date: Wed, 19 Nov 2003 21:00:44 -0800 (PST)
- Subject: RE: regarding transparent data ranges (in tracepoint support)
--- "Newman, Mark (N-Superior Technical Resource Inc)"
<mark.newman@lmco.com> wrote:
> Sorry about the tunnel vision. When the SUT exits
> we loose all of the
> tracepoint data in target memory. Stopping that from
> happening is the
> next thing on my list after I finish making
> interrupt work. After the
> program finishes it should not exit without an ok
> from the engineer.
>
> So Ankit if that is what you are looking to do I
> agree completely.
> However can't gdbserver do something more like the
> restart that occurs
> with a "w" or "x" status after the putpkt in the
> case statement in
> server.c
>
> Mark
>
thanks for the solution Mark.restarting the
debuggee would surely work,just that some overhead may
be involved.but it sort of gives me a feeling of
hacking around the solution since the debuggee would
be run twice,2'nd time just for the transparent data
ranges. thanks for the solution anyway.
any comments on PTRACE_EVENT_EXIT ??
Ankit.
__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/