<!DOCTYPE html> <html> <head> <title>Linux Studio Plugins Project</title> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> <link rel="stylesheet" href="../../css/style.css" type="text/css"> </head> <body> <div id="body"> <!-- Header --> <div id="header"> <img src="../../img/header.png" alt="Linux Studio Plugins Project" > </div> <!-- Navigation top --> <div id="menu"> <ul> <li class="sel">Profiling and Debugging</li> <li><a href="../../index.html">Home</a></li> </ul> </div> <!-- Main content --> <div id="main"> <h1>Profiling and Debugging</h1><p> To profile code, untar special profiling release into directory on the file system and simply launch it: </p> <pre>tar xzf lsp-plugins-profile-<version>-<arch>.tar.gz cd lsp-plugins-profile-<version>-<arch> ./lsp-plugins-profile <plugin-id> </pre> <p> After the execution, the profiling file 'gmon.out' will be generated. To generate profiling information, issue the gprof command: </p> <pre>gprof ./lsp-plugins-profile gmon.out >lsp-plugins.profile </pre> <p> For debugging purposes the GNU Debugger (gdb) may be used: </p> <pre>gdb --args ./lsp-plugins-profile <plugin-id> </pre> <p> For debugging and getting crash stack trace with Ardour, please follow these steps: </p> <ul> <li>Open console</li> <li>Run ardour from console with --gdb option</li> <li>After gdb starts, issue 'run' command</li> <li>Do usual stuff to reproduce the problem</li> <li>After Ardour crashes, type 'thread apply all bt' in console and attach the output to the bug report. </li> </ul> </div> <!-- Navigation bottom --> <div id="menu"> <ul> <li class="sel">Profiling and Debugging</li> <li><a href="../../index.html">Home</a></li> </ul> </div> <!-- Footer --> <div id="footer"> <p>(C) Linux Studio Plugins, 2015-2016</p> <p>All rights reserved</p> </div> </div> </body> </html>
distrib
>
Mageia
>
7
>
armv7hl
>
media
>
core-release
>
by-pkgid
>
cacce3d33a6bb704cb067ff82f5844d8
>
files
>
371
