Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
frequently_asked_questions [2018/02/07 17:07]
127.0.0.1 external edit
frequently_asked_questions [2019/04/17 15:37] (current)
tedfelix [How to get a stack trace for a crash]
Line 59: Line 59:
  
 ====How to get a stack trace for a crash==== ====How to get a stack trace for a crash====
 +
 +First, make sure you are running a version of rosegarden that was built with debugging turned on.
 +
 +<​code>​
 +-DCMAKE_BUILD_TYPE=Debug
 +</​code>​
 +
 +Without debugging, there will be no symbols in the binary, and the backtrace will be useless. ​ You'll likely need to build rosegarden on your own to get a debug version. ​ Instructions can be found here: [[dev:​eclipse|Using the Eclipse IDE to work on Rosegarden]]
 +
 Open a terminal window, and check to ensure that applications will be able to produce core dumps. ​ The exact command and syntax may vary from shell to shell, but for bash it is ''​ulimit -a'':​ Open a terminal window, and check to ensure that applications will be able to produce core dumps. ​ The exact command and syntax may vary from shell to shell, but for bash it is ''​ulimit -a'':​
  
Line 75: Line 84:
 </​code>​ </​code>​
  
-Now start rosegarden from the command line, and reproduce the crash. You should now have a core file in your current directory. The core file is either named **core** or **core.<//​number//>​**.+Now start a **debug version** of rosegarden from the command line, and reproduce the crash. You should now have a core file in your current directory. The core file is either named **core** or **core.<//​number//>​**.
  
 Run ''​gdb'':​ Run ''​gdb'':​
 
 
frequently_asked_questions.1518019622.txt.gz ยท Last modified: 2018/02/07 17:07 by 127.0.0.1
Recent changes RSS feed Creative Commons License Valid XHTML 1.0 Valid CSS Driven by DokuWiki