Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
	       Jan Kratochvil <jan.kratochvil@redhat.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH 2/6] Introduce `pre_expanded sals'
Date: Fri, 29 Jul 2011 20:36:00 -0000	[thread overview]
Message-ID: <m3zkjxdlnt.fsf@redhat.com> (raw)
In-Reply-To: <m3vcun8xuo.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed,	27 Jul 2011 10:58:07 -0600")

Tom Tromey <tromey@redhat.com> writes:

>>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
>
> [ multi-location breakpoint stuff ]
> Pedro> I strongly suggest not relying on changing this as prerequisite
> Pedro> for stap support.
>
> Yesterday I started wondering if this patch series could go in if
> re-expressed as catchpoints.
>
> That is, instead of:
>
>    break probe:arg
>
> we would use:
>
>    catch probe arg

IMHO this is OK.  I would prefer to see this command as a breakpoint
because I have always seen catchpoints as "event-oriented breakpoints",
such as the calling/returning of a syscall, or a fork, or exec.  But
this is my understanding, so...

However, I think that the stap integration is an important feature and
shouldn't be blocked anymore.

> The drawback here is that the linespec approach works automatically with
> tracepoints.  We could fix this via a new argument to 'strace', say '-p'
> (for "probe").

Sounds good.

Regards,

Sergio.


  reply	other threads:[~2011-07-29 17:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  3:08 Sergio Durigan Junior
2011-04-06 20:13 ` Tom Tromey
2011-04-12 11:18   ` Pedro Alves
2011-04-12 11:53     ` Jan Kratochvil
2011-04-12 13:30       ` Pedro Alves
2011-04-12 20:34         ` Tom Tromey
2011-04-12 22:22         ` Matt Rice
2011-04-13  9:53           ` Eli Zaretskii
2011-07-27 17:08         ` Tom Tromey
2011-07-29 20:36           ` Sergio Durigan Junior [this message]
2011-08-04 20:41             ` Tom Tromey
2011-08-05  3:41               ` Sergio Durigan Junior
2011-08-05 14:40                 ` Tom Tromey
2011-08-05 18:06                   ` Sergio Durigan Junior
2011-08-10 14:24           ` Tom Tromey
2011-05-03 16:09       ` Jerome Guitton
2011-05-03 18:17         ` Joel Brobecker
2011-04-12 20:26     ` Tom Tromey
2011-04-13  9:51       ` Eli Zaretskii
2011-04-13 19:20         ` Tom Tromey
2011-04-15 10:37           ` Eli Zaretskii
2011-04-18 18:37       ` Pedro Alves
2011-04-27 18:02         ` Jan Kratochvil
2011-04-29 20:42         ` Tom Tromey
2011-04-11 21:08 ` Jan Kratochvil

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=m3zkjxdlnt.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=pedro@codesourcery.com \
    --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