On Monday 26 January 2015 17:10:34 Fernanda Monteiro wrote:
> Hi Christian, thanks for the tip. I've just recompiled with debug symbols
> but I'm in doubt about how to backtrace it as a LV2 plugin, since if I run
> LinuxSampler prior to it, plugin will just fail due to can't bind to the
> right port anyway, so I can't have LS running before that in gdb. Any
> suggestions?
Same thing. Just that you start Ardour instead of LinuxSampler in the way
described. However since LinuxSampler is then launched by Ardour as plugin,
you must install LinuxSampler before launching Ardour. Compiling Ardour with
debugging symbols turned on as well, is definitely recommended.
Another option (instead of starting Ardour with gdb) is enabling coredump
output on your system:
ulimit -c unlimited
Then you can run Ardour normally (without debugger). Once it crashes it will
automatically write a core dump file to the local directory, which is
essentially a memory dump of the Ardour process at the time when the crashed
happened. You can then get the back trace like this:
gdb /full/path/to/ardourbinary /full/path/to/coredumpfile
bt
Both solutions usually yield the same result.
CU
Christian
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
