Documentation/devtools/maemo5/ltrace
(New page: == Description == Ltrace traces both system and library calls. Ltrace is quite similar to strace the main differences being: * ltrace can trace ...) |
(devtools template) |
||
(2 intermediate revisions not shown) | |||
Line 1: | Line 1: | ||
+ | {{Devtools}} | ||
+ | |||
+ | |||
== Description == | == Description == | ||
Line 29: | Line 32: | ||
== See Also == | == See Also == | ||
- | [[Documentation/devtools/maemo5/strace|strace]] | + | [[Documentation/devtools/maemo5/strace|strace]], |
+ | [[Documentation/devtools/maemo5/latrace|latrace]] | ||
+ | |||
+ | [[Category:Fremantle]] |
Latest revision as of 15:13, 11 March 2010
This article documents a developer tool. A list of available devtools is available, together with installation instructions. |
Contents |
[edit] Description
Ltrace traces both system and library calls.
Ltrace is quite similar to strace the main differences being:
- ltrace can trace also function calls between shared libraries.
- ltrace does not work over clone(). If threading or forking is used, ltrace needs to be attached to the process after that has happened.
[edit] Packages
source: ltrace
binary: ltrace
[edit] Usage Examples
Attach to the process with process id pid and begin tracing:
# ltrace -p pid
[edit] Links
[ltrace man page](/development/documentation/man_pages/ltrace.html)
[edit] See Also
- This page was last modified on 11 March 2010, at 15:13.
- This page has been accessed 8,050 times.