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: FW: tracepoint frames
Date: Tue, 07 Oct 2003 04:20:00 -0000 [thread overview]
Message-ID: <vt28ynxvfvp.fsf@zenia.home> (raw)
In-Reply-To: <F56FBA314E8E5A41895F0DA8F6716A6D02A4C5@EMSS04M11.us.lmco.com>
"Newman, Mark (N-Superior Technical Resource Inc)" <mark.newman@lmco.com> writes:
> > Right, but GDB could request more information from the stub when it
> > creates the tracepoint. The stub shouldn't have to collect
> > anything at
> > all that GDB didn't tell it to.
> >
>
> That is an interesting point! This could be left up to the user.
>
> Would that be acceptable to the community?
If I understand what's been said, that's the way the existing
tracepoint support works --- you have to tell it everything you want
to collect. If you have selected a tracepoint hit and you ask for
something that wasn't collected, you get an error.
prev parent reply other threads:[~2003-10-07 4:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 15:08 Newman, Mark (N-Superior Technical Resource Inc)
2003-10-07 4:20 ` Jim Blandy [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=vt28ynxvfvp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).