Project

General

Profile

Actions
Copy link

Bug #486

closed

Can not successfully launch instrumented app (that are compiled with lttng 2.1) when latest lttng (origin/master) is loaded and a session is active

Added by Tan le tran about 11 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Critical
Assignee:
-
Target version:
LTTng - 2.2
Start date:
03/27/2013
Due date:
% Done:

100%

Estimated time:

Description


Problem Description:
====================
 * When launching an instrumented app (which is compiled with lttng 2.1) on a 
   system that has lttng latest origin/master loaded (and an active session 
   is present), then the instrumented app either segfault or gives the following
   error message:
       "error while loading shared libraries: liburcu-bp.so.1: cannot open shared 
        object file: No such file or directory" 

   The instrumented app segfault when the following commits were used:
       userspace   : 8a97780 (HEAD, origin/stable-0.7) Fix: tests/api.h use cpuset.h
       lttng-tools : 8f3f773 (HEAD, origin/master, origin/HEAD, globalBuffer) Fix: lttng UI ...
       lttng-ust   : d3db6a4 (HEAD, origin/master, origin/HEAD) Performance: add unlikely ...

   The instrumented app fails to launch with error "error while loading shared libraries: 
   liburcu-bp.so.1: cannot open shared object file: No such file or directory" 
   when the following commit were used:
       userspace : d107390 (HEAD, origin/master, origin/HEAD, globalBuffer) Add tab to output ...
       lttng-tools : e2ad3b4 (HEAD, origin/master, origin/HEAD, globalBuffer) Add demo README
       lttng-ust : 9f9ee9c (HEAD, origin/master, origin/HEAD, globalBuffer) Fix: UST context activation

Is problem reproducible ?
=========================
   Yes

How to reproduce (if reproducible):
===================================
 Scenario1 (when usersapce 0.7 is used)
   0)_ Use the following commits:
       userspace   : 8a97780 (HEAD, origin/stable-0.7) Fix: tests/api.h use cpuset.h
       lttng-tools : 8f3f773 (HEAD, origin/master, origin/HEAD, globalBuffer) Fix: lttng UI ...
       lttng-ust   : d3db6a4 (HEAD, origin/master, origin/HEAD) Performance: add unlikely ...
   1)_ Compile an instrumented app with lttng 2.1 library
   2)_ Load lttng from origin/master branch
   3)_ Launch the instr app (from step-1)
       lttng list -u   #-- shows that the app is registered to sessionD

   4)_ lttng create s
       lttng enable-event -u "com*" 
       lttng start
   5)_ The app will segfault as soon as the session is started.
   6)_ Relaunch the app again
       The app will segfault right away.

 Scenario2 (when latest origin/master userspace is used)
   0)_ Use the following commits:
       userspace : d107390 (HEAD, origin/master, origin/HEAD, globalBuffer) Add tab to output ...
       lttng-tools : e2ad3b4 (HEAD, origin/master, origin/HEAD, globalBuffer) Add demo README
       lttng-ust : 9f9ee9c (HEAD, origin/master, origin/HEAD, globalBuffer) Fix: UST context activation

   1)_ Compile an instrumented app with lttng 2.1 library
   2)_ Load lttng from origin/master branch
   3)_ Launch the instr app (from step-1)
       The app fail to launch with the following error:
           "error while loading shared libraries: liburcu-bp.so.1: cannot 
            open shared object file: No such file or directory" 

Commit used:
============
  Please see description above.

Files

Download all files
InstApp_Segfault.log (107 KB) InstApp_Segfault.log log for scenario1 Tan le tran, 03/27/2013 10:22 AM
InstApp_LaunchError.log (11.4 KB) InstApp_LaunchError.log log for scenario2 Tan le tran, 03/27/2013 10:22 AM
Actions
Copy link
 #1

Updated by David Goulet about 11 years ago

  • Status changed from New to Feedback
  • Priority changed from Normal to High
  • Target version set to 2.2

This is unfortunately a normal behavior. Using lttng-tools 2.2, you absolutely needs the UST tracer 2.2. With 2.2-rc1 release, the tracer SHOULD NOT register because of the version mismatch of the tracer/tools.

The 2.2-rc1 release should have fix that. If not, let me know because that would be a critical issue we have to fix.

Thanks!

Actions
Copy link
 #2

Updated by Mathieu Desnoyers about 11 years ago

  • Project changed from LTTng-tools to LTTng-UST
  • Priority changed from High to Critical
Actions
Copy link
 #3

Updated by Mathieu Desnoyers about 11 years ago

Will discuss only the first scenario in this bug entry. See bug #498 for scenario 2.

Scenario1 (when usersapce 0.7 is used)
   0)_ Use the following commits:
       userspace   : 8a97780 (HEAD, origin/stable-0.7) Fix: tests/api.h use cpuset.h
       lttng-tools : 8f3f773 (HEAD, origin/master, origin/HEAD, globalBuffer) Fix: lttng UI ...
       lttng-ust   : d3db6a4 (HEAD, origin/master, origin/HEAD) Performance: add unlikely ...
   1)_ Compile an instrumented app with lttng 2.1 library
   2)_ Load lttng from origin/master branch
   3)_ Launch the instr app (from step-1)
       lttng list u   #- shows that the app is registered to sessionD
4)_ lttng create s
       lttng enable-event -u "com*" 
       lttng start
   5)_ The app will segfault as soon as the session is started.
   6)_ Relaunch the app again
       The app will segfault right away.
Actions
Copy link
 #4

Updated by Mathieu Desnoyers about 11 years ago

  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF