From: Sergio Durigan Junior <sergiodj@redhat.com>
To: jose.marchesi@oracle.com (Jose E. Marchesi)
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 5/9] New probe type: DTrace USDT probes.
Date: Fri, 10 Oct 2014 18:44:00 -0000 [thread overview]
Message-ID: <87d29z228q.fsf@redhat.com> (raw)
In-Reply-To: <87lhondb4y.fsf@oracle.com> (Jose E. Marchesi's message of "Fri, 10 Oct 2014 20:37:17 +0200")
On Friday, October 10 2014, Jose E. Marchesi wrote:
> > You should free the enablers VEC in the end of the function. You could
> > probably make a cleanup and call it later.
> >
> > Hmm, I don't see the need of doing a deep copy of the vector, nor I
> > remember why I felt it was necessary to do it when I wrote the original
> > code.
> >
> > I changed that to:
> >
> > /* Add the vector of enablers to this probe, if any. */
> > ret->enablers = enablers;
> >
> > But maybe(probably) I am missing something? :?
>
> Hm, right. But if you do that, you will have to adjust
> dtrace_probe_destroy, because it will be freeing the same 'enablers'
> over and over...
>
> Aaah, that was indeed the reason! A "DOF probe" translates into 0 or
> more gdb probes, and they all share the same vector of enablers.
>
> Maintaining a copy of the enablers per gdb probe makes it trivial to
> manage its memory. Otherwise we would need to keep track of which
> enabler vectors are shared by which gdb probes... argh!
>
> I will roll back to the deep copy approach :)
:-)
And then you need that cleanup I mentioned before :-P.
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2014-10-10 18:44 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 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 8/9] Documentation for DTrace USDT probes 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-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 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 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 5/9] New probe type: " 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 [this message]
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 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 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-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
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=87d29z228q.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.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