public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: jose.marchesi@oracle.com (Jose E. Marchesi)
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/9] Add support for DTrace USDT probes to gdb
Date: Thu, 09 Oct 2014 08:05:00 -0000	[thread overview]
Message-ID: <87wq894q9x.fsf@oracle.com> (raw)
In-Reply-To: <87zjd69wox.fsf@redhat.com> (Sergio Durigan Junior's message of	"Wed, 08 Oct 2014 15:40:46 -0400")


Hi Sergio.

    > This patch series introduces support in GDB for a new type of probe:
    > DTrace USDT probes.
    >
    > The first three patches do some changes to the existing probe.[ch]
    > code, fixing some minor problems associated to support several probe
    > types, having several probes of different types defined in the same
    > object and supporting the notion of enabling and disabling probes.
    >
    > The rest of the patches are the implementation of the new probe type,
    > including target support for x86_64 targets, a testsuite and
    > documentation.
    
    OK, I think I reviewed all the patches (except the docs).  First of all,
    thanks for doing this!

Heh, thanks for the throughout review!
    
    I have mixed feelings about the inclusion of this feature.  While I
    obviously agree that support for a new probe type is good, I also don't
    like the fact that we are talking about a feature that relies on
    proprietary software (Oracle dtrace) to operate.

As you know I am sympathetic with your concerns.  Was I in your position
I would raise exactly the same point.

    You mentioned that you were going to try to come up with some way to
    test this feature using a tweaked asm source.  I think this is a good
    progress already, and I am looking forward to seeing this.

Yes, I am working in a .s file that, once compiled and linked, will
provide the DOF program corresponding to the testcase.  That will not
replace dtrace -G for the general usage, and will have to be updated
should the testcase change, but at least will allow to test the probe
support without having to install proprietary software.
    
    Either way, if we decide to include this feature on GDB, you (or someone
    else from Oracle) will be responsible for it, because we outside Oracle
    have no way to make sure that it doesn't break.

I can certainly take responsibility on it.
    
    Having said that, I will wait until you post updated patches with our
    comments addressed (and hopefully with a nice testcase :-P), and then we
    can continue this discussion :-).

I will post a corrected version of the patch series soon.
Thanks again!

      reply	other threads:[~2014-10-09  8:05 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <no>
2012-04-18  9:27 ` [RFA] Add proper handling for internal functions and STT_GNU_IFUNC symbols in Ada mode Paul Hilfinger
2012-04-18 14:45   ` Joel Brobecker
2012-04-22 15:33   ` [committed] " Paul Hilfinger
2014-09-26  9:43 ` [PATCH 0/9] Add support for DTrace USDT probes to gdb Jose E. Marchesi
2014-09-26  9:43   ` [PATCH 4/9] New gdbarch functions: dtrace_probe_argument, dtrace_probe_is_enabled, dtrace_enable_probe, dtrace_disable_probe Jose E. Marchesi
2014-10-02 21:34     ` Sergio Durigan Junior
2014-10-10 16:38       ` Jose E. Marchesi
2014-09-26  9:43   ` [PATCH 2/9] Move `compute_probe_arg' and `compile_probe_arg' to probe.c Jose E. Marchesi
2014-09-30  0:02     ` Sergio Durigan Junior
2014-10-10 16:38       ` Jose E. Marchesi
2014-09-26  9:43   ` [PATCH 1/9] Adapt `info probes' to support printing probes of different types Jose E. Marchesi
2014-09-29 21:15     ` Sergio Durigan Junior
2014-10-10 16:38       ` Jose E. Marchesi
2014-09-26  9:43   ` [PATCH 7/9] Simple testsuite for DTrace USDT probes Jose E. Marchesi
2014-10-08 19:30     ` Sergio Durigan Junior
2014-10-10 16:38       ` Jose E. Marchesi
2014-09-26  9:43   ` [PATCH 9/9] Announce the DTrace USDT probes support in NEWS Jose E. Marchesi
2014-09-26 13:12     ` Eli Zaretskii
2014-09-29 10:29       ` Jose E. Marchesi
2014-09-26  9:43   ` [PATCH 6/9] Support for DTrace USDT probes in x86_64 targets Jose E. Marchesi
2014-10-08 19:32     ` Sergio Durigan Junior
2014-10-10 16:38       ` Jose E. Marchesi
2014-09-26  9:43   ` [PATCH 3/9] New commands `enable probe' and `disable probe' Jose E. Marchesi
2014-09-26 13:11     ` Eli Zaretskii
2014-09-29 10:26       ` Jose E. Marchesi
2014-09-30 23:13     ` Sergio Durigan Junior
2014-09-30 23:20       ` Sergio Durigan Junior
2014-10-10 16:38       ` Jose E. Marchesi
2014-09-26  9:43   ` [PATCH 5/9] New probe type: DTrace USDT probes Jose E. Marchesi
2014-09-26 13:19     ` Eli Zaretskii
2014-10-02 23:19     ` Sergio Durigan Junior
2014-10-10 16:38       ` Jose E. Marchesi
2014-10-10 18:13         ` Sergio Durigan Junior
2014-10-10 18:32           ` Jose E. Marchesi
2014-10-10 18:44             ` Sergio Durigan Junior
2014-09-26  9:43   ` [PATCH 8/9] Documentation for " Jose E. Marchesi
2014-09-26 13:18     ` Eli Zaretskii
2014-09-29 10:26       ` Jose E. Marchesi
2014-09-29 13:35         ` Eli Zaretskii
2014-09-29 13:53           ` Jose E. Marchesi
2014-10-08 19:40   ` [PATCH 0/9] Add support for DTrace USDT probes to gdb Sergio Durigan Junior
2014-10-09  8:05     ` Jose E. Marchesi [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=87wq894q9x.fsf@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).