Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stan Shebs <stan@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Infer $pc in a file's trace frame
Date: Sun, 04 Apr 2010 23:25:00 -0000	[thread overview]
Message-ID: <4BB91FBA.8090908@codesourcery.com> (raw)
In-Reply-To: <83tyruwd0a.fsf@gnu.org>

Eli Zaretskii wrote:
> This is okay, but the last two sentences leave so much stuff
> unexplained that I doubt the reader will be able to understand their
> meaning, unless she is a tracepoint hacker.  [...]

It is a little obscure to explain, in fact it's a fundamental flaw of 
the tdump implementation that I didn't fully understand myself until 
recently.

What I did for now was to whack those last two sentences, and add a 
couple more paragraphs in the tdump description.  After writing them, my 
main thought is "what a lame design, can't we do tdump better?".  :-)  
So perhaps after gdbserver tracepoints go in and more people get some 
familiarity, we should revisit both code and  documentation.

Stan


      reply	other threads:[~2010-04-04 23:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 22:15 Stan Shebs
2010-04-02  7:05 ` Eli Zaretskii
2010-04-04 23:25   ` Stan Shebs [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=4BB91FBA.8090908@codesourcery.com \
    --to=stan@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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