From: MONTET Julien via lttng-dev <lttng-dev@lists.lttng.org>
To: Jonathan Rajotte-Julien <jonathan.rajotte-julien@efficios.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Issues on basic LTTng trace userspace (tutorial)
Date: Wed, 24 Mar 2021 19:08:27 +0000 [thread overview]
Message-ID: <PR3PR02MB62025CCA7D6372430CC89AF7D1639@PR3PR02MB6202.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <20210324190053.GG344120@joraj-alpa>
[-- Attachment #1.1: Type: text/plain, Size: 1675 bytes --]
Hi Jonathan,
Thank you so much, it is 100% working.
Let's enjoy LTTng !!!
Have a nice day,
________________________________
De : Jonathan Rajotte-Julien <jonathan.rajotte-julien@efficios.com>
Envoyé : mercredi 24 mars 2021 20:00
À : MONTET Julien <julien.montet@reseau.eseo.fr>
Cc : lttng-dev <lttng-dev@lists.lttng.org>
Objet : Re: [lttng-dev] Issues on basic LTTng trace userspace (tutorial)
On Wed, Mar 24, 2021 at 06:55:37PM +0000, MONTET Julien wrote:
> Hi Jonathan,
>
> You are absolutely right !
> I have two different lttng : find /usr -name "*liblttng-ust*" Ubuntu Pastebin<https://paste.ubuntu.com/p/NVtXPhj4fW/>
Glad to know that we are making progress.
>
> According to you, what would be the best solution to solve this issue ?
> I have indeed a folder named lttng-ust where I have made the (wrong) configure / make.
Go into the lttng folder and do:
sudo make uninstall
sudo ldconfig
>
>
> I tried to (temporary) remove all the libttng* /usr/local/lib/, but I face this problem :
That should works also.
> /usr/bin/ld: hello-tp.o: in function `__lttng_events_init__hello_world':
> hello-tp.c:(.text+0xe56): undefined reference to `lttng_ust_probe_register'
> /usr/bin/ld: hello-tp.o: in function `__lttng_events_exit__hello_world':
> hello-tp.c:(.text+0xeb2): undefined reference to `lttng_ust_probe_unregister'
> collect2: error: ld returned 1 exit status
Did you remove the -L/usr/local/bin flag? There should be no reason to keep it
at this point.
>
> In the worst case scenario I am able to get my last clean snapchot.
That is also a good bet :).
--
Jonathan Rajotte-Julien
EfficiOS
[-- Attachment #1.2: Type: text/html, Size: 3859 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2021-03-24 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 11:29 [lttng-dev] Issues on basic LTTng trace userspace (tutorial) MONTET Julien via lttng-dev
2021-03-24 14:25 ` Jonathan Rajotte-Julien via lttng-dev
[not found] ` <PR3PR02MB6202F969540C279A6A171F83D1639@PR3PR02MB6202.eurprd02.prod.outlook.com>
2021-03-24 15:32 ` Jonathan Rajotte-Julien via lttng-dev
2021-03-24 15:53 ` MONTET Julien via lttng-dev
2021-03-24 16:06 ` Jonathan Rajotte-Julien via lttng-dev
2021-03-24 16:36 ` Jonathan Rajotte-Julien via lttng-dev
2021-03-24 18:55 ` MONTET Julien via lttng-dev
2021-03-24 19:00 ` Jonathan Rajotte-Julien via lttng-dev
2021-03-24 19:08 ` MONTET Julien via lttng-dev [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=PR3PR02MB62025CCA7D6372430CC89AF7D1639@PR3PR02MB6202.eurprd02.prod.outlook.com \
--to=lttng-dev@lists.lttng.org \
--cc=jonathan.rajotte-julien@efficios.com \
--cc=julien.montet@reseau.eseo.fr \
/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 NNTP newsgroup(s).