From: tracemein@gmail.com (Naren)
Subject: [ltt-dev] UST - Problems in recording trace on a current process
Date: Fri, 12 Feb 2010 10:10:20 +0100 [thread overview]
Message-ID: <19fa8ef31002120110x2aa20103x9e1cdb2e502b6b5f@mail.gmail.com> (raw)
Message-ID: <20100212091020.IDRcQxya3K1vGAHbBZMlmjTHvwIV1uZ9SYUWkl1TaGk@z> (raw)
In-Reply-To: <201002111918.52101.pierre-marc.fournier@polymtl.ca>
Hi Pierre
>>No. Flight recorder is not yet supported. There is no way to activate it.
>>
>>Gimp is multi-process application, so you must use libinterfork.so. Did
you
>>LD_PRELOAD it?
Yes, I did LD_PRELOAD libust,libinterfork and libmallocwrap with Firefox not
with Gimp. I guess firefox,on startup, is not a multiprocess application in
the sense that it spawns only a single process. In contrasts, Gimp spawns
two processes.
Hence, LD_PRELOADing libust,libinterfork and libmallocwrap with Firefox
would not yield significant results. I will try the same with Gimp and get
back to you.
Regards
Naren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100212/e4c9864f/attachment-0002.htm>
next prev parent reply other threads:[~2010-02-12 9:10 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 21:49 Naren
2010-02-08 21:49 ` Naren
2010-02-08 22:19 ` Pierre-Marc Fournier
[not found] ` <19fa8ef31002081428x1e215acfgd81d505ee359ce9@mail.gmail.com>
[not found] ` <201002081744.06912.pierre-marc.fournier@polymtl.ca>
2010-02-08 23:54 ` Naren
2010-02-08 23:54 ` Naren
2010-02-09 1:37 ` soumyakanti chakraborty
2010-02-09 1:37 ` soumyakanti chakraborty
2010-02-09 1:48 ` soumyakanti chakraborty
2010-02-09 1:48 ` soumyakanti chakraborty
2010-02-09 5:45 ` Pierre-Marc Fournier
2010-02-09 14:44 ` Naren
2010-02-09 14:44 ` Naren
2010-02-09 14:51 ` Douglas Santos
2010-02-09 14:51 ` Douglas Santos
2010-02-09 16:43 ` Naren
2010-02-09 16:43 ` Naren
2010-02-09 17:11 ` Pierre-Marc Fournier
2010-02-09 16:42 ` Pierre-Marc Fournier
2010-02-09 17:11 ` Naren
2010-02-09 17:11 ` Naren
2010-02-09 17:25 ` Pierre-Marc Fournier
2010-02-09 20:40 ` Naren
2010-02-09 20:40 ` Naren
2010-02-09 21:25 ` Douglas Santos
2010-02-09 21:28 ` Pierre-Marc Fournier
2010-02-10 0:50 ` Naren
2010-02-10 0:50 ` Naren
2010-02-10 15:26 ` Pierre-Marc Fournier
2010-02-10 16:53 ` Naren
2010-02-10 16:53 ` Naren
2010-02-10 20:15 ` Pierre-Marc Fournier
2010-02-10 22:08 ` Naren
2010-02-10 22:08 ` Naren
2010-02-12 0:18 ` Pierre-Marc Fournier
2010-02-12 9:10 ` Naren [this message]
2010-02-12 9:10 ` Naren
2010-02-15 6:04 ` Pierre-Marc Fournier
2010-02-15 6:23 ` Naveh, Ido
2010-02-15 12:16 ` Mathieu Desnoyers
2010-02-15 11:42 ` Naren
2010-02-15 11:42 ` Naren
2010-02-15 14:53 ` Pierre-Marc Fournier
2010-02-18 17:47 ` Pierre-Marc Fournier
2010-02-18 22:58 ` Naren
2010-02-18 22:58 ` Naren
2010-02-18 22:58 ` Naren
2010-02-19 16:50 ` Pierre-Marc Fournier
2010-02-19 17:15 ` Naren
2010-02-19 17:15 ` Naren
2010-02-19 17:15 ` Naren
2010-02-22 0:46 ` soumyakanti chakraborty
2010-02-22 0:46 ` soumyakanti chakraborty
2010-02-22 0:46 ` soumyakanti chakraborty
2010-02-23 15:15 ` Pierre-Marc Fournier
2010-02-26 1:55 ` soumyakanti chakraborty
2010-02-26 1:55 ` soumyakanti chakraborty
2010-02-26 1:55 ` soumyakanti chakraborty
2010-02-26 5:35 ` Pierre-Marc Fournier
2010-02-09 14:46 ` Douglas Santos
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=19fa8ef31002120110x2aa20103x9e1cdb2e502b6b5f@mail.gmail.com \
--to=tracemein@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