From: Tom Tromey <tromey@redhat.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [MI tracepoints 5/9] -break-passcount
Date: Tue, 16 Mar 2010 16:23:00 -0000 [thread overview]
Message-ID: <m37hpcb5hh.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201003161905.27202.vladimir@codesourcery.com> (Vladimir Prus's message of "Tue, 16 Mar 2010 19:05:27 +0300")
>>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:
Tom> It is odd to have a command named -break-passcount that can't actually
Tom> be used on breakpoints
Volodya> It can -- just not on all kinds of breakpoints.
Ok. Maybe you could explain how -break-passcount and -break-after are
different, without referring to "tracepoints" as something separate from
"breakpoints".
Tom> -- and that will never be usable on breakpoints.
Volodya> You mean, on "ordinary" breakpoints? It's totally unclear --
Volodya> while presently tracing breakpoints are always target assisted,
Volodya> we may in future implement a software tracing breakpoints,
Volodya> where GDB would execute the commands implicitly for user.
I was just basing this observation on your own statement that merging
-break-passcount and -break-after doesn't make sense.
Tom
next prev parent reply other threads:[~2010-03-16 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 8:56 Vladimir Prus
2010-03-15 21:04 ` Tom Tromey
2010-03-16 12:13 ` Vladimir Prus
2010-03-16 15:37 ` Tom Tromey
2010-03-16 15:47 ` Vladimir Prus
2010-03-16 15:56 ` Tom Tromey
2010-03-16 16:05 ` Vladimir Prus
2010-03-16 16:23 ` Tom Tromey [this message]
2010-03-16 17:07 ` Vladimir Prus
2010-03-16 17:11 ` Tom Tromey
2010-03-16 18:06 ` Marc Khouzam
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=m37hpcb5hh.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@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