[lttng-dev] Problem with Babeltrace

[lttng-dev] Problem with Babeltrace

[Tim Tannert]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]

Hey,

everytime when I start babeltrace:
babeltrace --version

or
lttng view

I'll get following message:
babeltrace: symbol lookup error: babeltrace: undefined symbol: opt_debug_info_full_path



Have somebody a idea how to fix?

Tim
Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20161024/21065db9/attachment.html>

[lttng-dev] Problem with Babeltrace

[Nathan Lynch]

On 10/24/2016 03:30 AM, Tim Tannert wrote:
> Hey,
> 
> everytime when I start babeltrace:
> *babeltrace --version*
> 
> or
> *lttng view
> 
> *I'll get following message:
> babeltrace: symbol lookup error: babeltrace: undefined symbol:
> opt_debug_info_full_path
> 

Seems your babeltrace installation is missing the ctf-text shared
object, which is where that symbol is defined.

Please folow up to the list with the version of babeltrace you are
using, and describe how it was installed (e.g. built from source or
using distribution package).

[lttng-dev] Problem with Babeltrace

[Simon Marchi]

On 2016-10-24 11:31, Nathan Lynch wrote:
> On 10/24/2016 03:30 AM, Tim Tannert wrote:
>> Hey,
>> 
>> everytime when I start babeltrace:
>> *babeltrace --version*
>> 
>> or
>> *lttng view
>> 
>> *I'll get following message:
>> babeltrace: symbol lookup error: babeltrace: undefined symbol:
>> opt_debug_info_full_path
>> 
> 
> Seems your babeltrace installation is missing the ctf-text shared
> object, which is where that symbol is defined.
> 
> Please folow up to the list with the version of babeltrace you are
> using, and describe how it was installed (e.g. built from source or
> using distribution package).

It would also be good to verify that you don't have multiple version of 
babeltrace installed.  For example, an older version installed by the 
package manager in /usr and a hand-compiled one in /usr/local.  
Executing the binary from /usr/local/bin/babeltrace could somehow load 
the shared library from /usr/lib, or vice-versa.

[lttng-dev] Problem with Babeltrace

[Philippe Proulx]

On Mon, Oct 24, 2016 at 11:35 AM, Simon Marchi <simark at simark.ca> wrote:
> On 2016-10-24 11:31, Nathan Lynch wrote:
>>
>> On 10/24/2016 03:30 AM, Tim Tannert wrote:
>>>
>>> Hey,
>>>
>>> everytime when I start babeltrace:
>>> *babeltrace --version*
>>>
>>> or
>>> *lttng view
>>>
>>> *I'll get following message:
>>> babeltrace: symbol lookup error: babeltrace: undefined symbol:
>>> opt_debug_info_full_path
>>>
>>
>> Seems your babeltrace installation is missing the ctf-text shared
>> object, which is where that symbol is defined.
>>
>> Please folow up to the list with the version of babeltrace you are
>> using, and describe how it was installed (e.g. built from source or
>> using distribution package).
>
>
> It would also be good to verify that you don't have multiple version of
> babeltrace installed.  For example, an older version installed by the
> package manager in /usr and a hand-compiled one in /usr/local.  Executing
> the binary from /usr/local/bin/babeltrace could somehow load the shared
> library from /usr/lib, or vice-versa.

This would only be true if the Babeltrace libraries are removed from
/usr/local/lib afterwards, but keeping /usr/local/bin/babeltrace,
because as far as I know, unless the distribution's package somehow
removes it, the executable is built with an explicit RPATH to locate its
own libraries, and this is the first place libraries are searched for.

Hence having multiple installations of Babeltrace is usually not a
problem, unless you mess with the file system manually.

Phil

>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev