Commit | Line | Data |
---|---|---|
5e0cbfb0 PP |
1 | --- |
2 | id: instrumenting-32-bit-app-on-64-bit-system | |
3 | --- | |
4 | ||
5 | In order to trace a 32-bit application running on a 64-bit system, | |
6 | LTTng must use a dedicated 32-bit | |
7 | [consumer daemon](#doc-lttng-consumerd). This section discusses how to | |
8 | build that daemon (which is _not_ part of the default 64-bit LTTng | |
9 | build) and the LTTng 32-bit tracing libraries, and how to instrument | |
10 | a 32-bit application in that context. | |
11 | ||
12 | Make sure you install all 32-bit versions of LTTng dependencies. | |
13 | Their names can be found in the `README.md` files of each LTTng package | |
47bfcb75 | 14 | source. How to find and install them depends on your target's |
5e0cbfb0 | 15 | Linux distribution. `gcc-multilib` is a common package name for the |
47bfcb75 | 16 | multilib version of GCC, which you also need. |
5e0cbfb0 PP |
17 | |
18 | The following packages will be built for 32-bit support on a 64-bit | |
19 | system: <a href="http://urcu.so/" class="ext">Userspace RCU</a>, | |
20 | LTTng-UST and LTTng-tools. |