Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: "Newman,
	Mark (N-Superior Technical Resource Inc)" <mark.newman@lmco.com>
Cc: gdb@sources.redhat.com
Subject: Re: tracepoint frames
Date: Fri, 03 Oct 2003 23:57:00 -0000	[thread overview]
Message-ID: <vt28yo1g9iy.fsf@zenia.home> (raw)
In-Reply-To: <F56FBA314E8E5A41895F0DA8F6716A6D02A4BA@EMSS04M11.us.lmco.com>


"Newman, Mark (N-Superior Technical Resource Inc)" <mark.newman@lmco.com> writes:
> The question has come up as to what needs to be collected when a
> tracepoint is hit.  I understand that a "frame" needs to be
> collected.  Can someone tell me what a "frame" is.  Is it a stack
> frame, a trace frame, or what?

Well, we do have trace frames; a trace frame is the clump of
information collected for a single tracepoint hit.  It includes
registers, and assorted regions of memory.

You can also ask a trace frame to collect things like local variables,
arguments, or registers.  But all that gets parsed by the code in
tracepoint.c and turned into a 'struct collection_list', that's just a
set of registers, memory regions, and agent expressions to collect;
it's all parsed for you.  So at that level, there are no frames any
more --- everything is explicit

But I don't feel like I've answered the question.  In what context did
it come up?


  reply	other threads:[~2003-10-03 23:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03 15:56 Newman, Mark (N-Superior Technical Resource Inc)
2003-10-03 23:57 ` Jim Blandy [this message]
2003-10-06 13:03 Newman, Mark (N-Superior Technical Resource Inc)
2003-10-06 13:51 ` Daniel Jacobowitz
2003-10-06 14:01 Newman, Mark (N-Superior Technical Resource Inc)
2003-10-06 14:52 ` 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=vt28yo1g9iy.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=gdb@sources.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