From: abhi.abhinav240@gmail.com (Abhinav Ranjan)
Subject: [lttng-dev] Need Help In trace generation for malloc(), free() calls etc
Date: Thu, 14 May 2020 10:55:32 +0530 [thread overview]
Message-ID: <CAPC3er=7+wOR8CdtdU+PGGOgWLWMBy55jAR5jZzyzZr67mQuCA@mail.gmail.com> (raw)
In-Reply-To: <20200513180404.GB2381108@joraj-alpa>
Thank You Sir,
I am sorry for the inconvenience caused to you!
Surely I'll take care of every suggestion you passed on to me.
Once again I thank you for your wonderful help!
Stay Safe and Happy!!!
On Wed, 13 May 2020 at 23:34, Jonathan Rajotte-Julien <
jonathan.rajotte-julien at efficios.com> wrote:
> Hi Abhinav,
>
> Please keep the mailing list in CC for all communication:
> lttng-dev at lists.lttng.org
>
> If not, I am not interested in helping you further.
>
> On Wed, May 13, 2020 at 09:26:52PM +0530, Abhinav Ranjan wrote:
> > Hi! Jonathan thank you so much for your help and reply! Sure I'll not use
> > snapshot from next time and follow your advice.
> > In fact I figured out the issue, but Jonathan I have one specific doubt I
> > wanted to trace malloc , free call from my app only but after using
> lttng
> > enable-event --userspace lttng_ust_libc:malloc I am seeing several
> malloc (
> > in Trace Compass) probably from different tracepoints from
> lttng_ust_libc.
>
> You will see all malloc that the app does for its lifetime since you
> LD_PRELOAD
> the wrapper including any allocation lttng-ust does. Keep in mind that
> lttng-ust
> is not magic, lttng-ust spun threads and do some allocations to do its job.
>
> What outcome do you expect? We might be able to at least get you on the
> right
> path. In other word, what is your end goal?
>
> Cheers
>
>
--
Thanking You!
Regards,
Abhinav
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20200514/c2a37119/attachment.htm>
prev parent reply other threads:[~2020-05-14 5:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPC3ern8bkAJDnOwoYh2Om44Q2GWAPsh140FW_aPGVkdUmCwkw@mail.gmail.com>
2020-05-13 4:59 ` Abhinav Ranjan
2020-05-13 15:33 ` Jonathan Rajotte-Julien
[not found] ` <CAPC3erkfapoZu_WM=znEyj0ch1YiKeX7-JBiauoLh+Seee0TZA@mail.gmail.com>
2020-05-13 18:04 ` Jonathan Rajotte-Julien
2020-05-14 5:25 ` Abhinav Ranjan [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='CAPC3er=7+wOR8CdtdU+PGGOgWLWMBy55jAR5jZzyzZr67mQuCA@mail.gmail.com' \
--to=abhi.abhinav240@gmail.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