diff options
| author | José Fonseca <jfonseca@vmware.com> | 2015-01-20 15:39:50 +0000 |
|---|---|---|
| committer | José Fonseca <jfonseca@vmware.com> | 2015-01-20 15:39:50 +0000 |
| commit | 217c55f87ba3ac07425ad2aa218a4977a3d2452b (patch) | |
| tree | ee7c640fe63416e82c0f2e64b76096e15f5ef2e6 /docs/BUGS.markdown | |
| parent | 42545d0318cb69b56fe147705c51c7abda446180 (diff) | |
docs: Detail MacOSX debug instructions.
Diffstat (limited to 'docs/BUGS.markdown')
| -rw-r--r-- | docs/BUGS.markdown | 23 |
1 files changed, 18 insertions, 5 deletions
diff --git a/docs/BUGS.markdown b/docs/BUGS.markdown index d3c990ab..94e24647 100644 --- a/docs/BUGS.markdown +++ b/docs/BUGS.markdown @@ -172,22 +172,23 @@ incorrect inconsistent rendering, or viewing with the GUI) please: Obtaining stack back-traces =========================== - -Linux/MacOSX ------------- - Please rebuild apitrace with debugging information, by passing `-DCMAKE_BUILD_TYPE=Debug` to cmake, or editing its value in `CMakeCache.txt` and rebuilding. +Linux +----- + To obtain a stack back-trace, run the application with gdb from a terminal: $ gdb --args application arg1 arg2 ... (gdb) run ... (gdb) bt + ... + (gdb) quit -On Linux, to trace an application inside gdb invoke apitrace as: +To trace an application inside GDB invoke apitrace as: apitrace trace --verbose --debug application arg1 ... @@ -202,6 +203,18 @@ See also more detailed and Distro specific instructions: * http://live.gnome.org/GettingTraces +Mac OS X +-------- + +To trace an application inside LLDB and obtain a stack backtrace invoke apitrace as: + + $ apitrace trace --verbose --debug application arg1 ... + ... + (lldb) bt + ... + (lldb) quit + + Windows ------- |