On Donnerstag, 9. April 2020 16:12:42 CEST joo bian wrote:
> I can gladly generate the profiling for you guys, as I really wish for this
> problem to be solved as soon as possible. Do you have some suggestions for
> how to go about the profiling? In the linuxsampler configuration there are
> some arguments for detailed logging and debugging. Should I activate them?
Profiling is done by using an external development tool. That's not a built-in
feature of the sampler.
There are numerous profilers out there now. IMO e.g. OProfile was always a
good choice on Linux. There are various good howtos on the Internet how to
perform profiling with the profiler of your choice.
Just keep in mind that before you start profiling, the sampler must be
compiled with debugging symbols turned on, which means additionally to the -O3
flag you also have to add the -g flag.
Also: the sampler's binary must not be stripped after compilation, which e.g.
the Debian packaging scripts would do by default, because stripping removes
the debugging symbols from the binary again. For that reason I recommend you
to not even bother to install the sampler in this case, just type
CXXFLAGS="-O3 -g" ./configure && make
from the source file directory to compile it, then simply run the sampler with
src/linuxsampler
CU
Christian
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
