Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [MI tracepoints 5/9] -break-passcount
Date: Tue, 16 Mar 2010 15:47:00 -0000	[thread overview]
Message-ID: <201003161847.47956.vladimir@codesourcery.com> (raw)
In-Reply-To: <m3vdcwb7me.fsf@fleche.redhat.com>

On Tuesday 16 March 2010 18:37:13 Tom Tromey wrote:

> >>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:
> 
> Tom> Doesn't the use of get_tracepoint make it tracepoint-specific?
> Tom> Or is this changed somewhere in the patch series?
> 
> Volodya> I was confused. This command remains specific to tracepoint, there's
> Volodya> no patch (yet?) that merges -break-passcount and -break-after and
> Volodya> in fact, it's probably not a good idea.
> 
> In that case, shouldn't the new command be called -trace-passcount, not
> -break-passcount?

I am not sure. Given that tracepoints are special kind of breakpoint now,
I'd rather have -break-passcount, with -trace command reserversed for
overall control of tracing. After all, mixing -break-insert -a with
later -trace-passcount may be confusing.

Thanks,

-- 
Vladimir Prus
CodeSourcery
vladimir@codesourcery.com
(650) 331-3385 x722


  reply	other threads:[~2010-03-16 15:47 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 [this message]
2010-03-16 15:56         ` Tom Tromey
2010-03-16 16:05           ` Vladimir Prus
2010-03-16 16:23             ` Tom Tromey
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=201003161847.47956.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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