Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: ankit thukral <ankit_plug@yahoo.com>
To: "Newman,
	Mark \(N-Superior Technical Resource Inc\)"
	<mark.newman@lmco.com>, Daniel Jacobowitz <drow@mvista.com>
Cc: ankit thukral <ankit_plug@yahoo.com>,
	Jim Blandy <jimb@redhat.com>,
	gdb@sources.redhat.com
Subject: RE: regarding transparent data ranges (in tracepoint support)
Date: Thu, 20 Nov 2003 05:00:00 -0000	[thread overview]
Message-ID: <20031120050044.97408.qmail@web60110.mail.yahoo.com> (raw)
In-Reply-To: <F56FBA314E8E5A41895F0DA8F6716A6D02A1F4@EMSS04M11.us.lmco.com>


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


  parent reply	other threads:[~2003-11-20  5:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 19:51 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-19 20:22 ` Daniel Jacobowitz
2003-11-20  5:00 ` ankit thukral [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-29  6:56 Ramana Radhakrishnan
2003-11-28 17:35 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-28 19:23 ` Daniel Jacobowitz
2003-11-29  1:29   ` Mark Newman
2003-11-29  1:34     ` Daniel Jacobowitz
2003-11-29  2:08       ` Mark Newman
2003-11-29  5:41         ` Daniel Jacobowitz
2003-11-28 17:24 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-28 17:27 ` Daniel Jacobowitz
2003-11-25 16:09 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-21 18:41 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-19 19:35 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-19 19:38 ` Daniel Jacobowitz
2003-11-17 17:26 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-17 18:04 ` Ramana Radhakrishnan
2003-11-14 19:30 async operation Newman, Mark (N-Superior Technical Resource Inc)
2003-11-16  6:32 ` regarding transparent data ranges (in tracepoint support) ankit thukral
2003-11-19  7:40   ` Jim Blandy
2003-11-19 16:25     ` ankit thukral
2003-11-19 18:55       ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031120050044.97408.qmail@web60110.mail.yahoo.com \
    --to=ankit_plug@yahoo.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=mark.newman@lmco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox