Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Check original contents at tracepoints
Date: Thu, 27 May 2010 19:45:00 -0000	[thread overview]
Message-ID: <m37hmpgmpi.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4BD24BC1.4030103@codesourcery.com> (Stan Shebs's message of	"Fri, 23 Apr 2010 18:39:13 -0700")

>>>>> "Stan" == Stan Shebs <stan@codesourcery.com> writes:

Stan> So the idea of this patch is to record, at definition time, the
Stan> bytes that the tracepoint expects to overwrite when it is
Stan> downloaded for the trace run.  The agent then compares with what
Stan> is currently at that address, and refuses to start the run if
Stan> there is any discrepancy.

This seems like a reasonable sanity check to me.

Stan> Assuming the whole idea has merit, one of the open issues has been to
Stan> decide how many bytes to record.

I don't have much to add on this front, sorry.

Tom


      parent reply	other threads:[~2010-05-27 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-24  1:39 Stan Shebs
2010-04-24  6:32 ` Eli Zaretskii
2010-05-27 19:45 ` Tom Tromey [this message]

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=m37hmpgmpi.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=stan@codesourcery.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