6 Jul
2012
6 Jul
'12
5:30 p.m.
Am Freitag, den 06.07.2012, 17:15 +0200 schrieb jeremy(a)autostatic.com:
first you must build guitarix with the --debug flag (./waf configure
[options] --debug )
then run
gdb guitarix
(type run the on the gdb prompt).
Try to load a ladspa plug-in into guitarxi, when guitarix crash, type
backtrace
Hopefully I get a information from the backtrace were exactly guitarix
crashed.
greets
hermann
Am Freitag,
den 06.07.2012, 15:54 +0200 schrieb Jeremy Jongepier:
What kind of gdb session output would you like? And adding any LADSPA plug-in
makes guitarix crash and not start up again. If I rm
.config/guitarix/plugins/ladspa* guitarix starts up again.
Jeremy
On 07/06/12 15:26, Jeremy Jongepier wrote:
could you please send me the output from a gbd session ?
I cant reproduce it here.
greets
hermann
On 07/06/12 15:19, hermann wrote:
> Hi Jeremy
>
> Thanks for reporting the issue,
> it seems that there changed/moved some things when boost go to version
> 1.50 because then, libboost-system is needed. With boost 1.49, we didn't
> need it, but build with boost > 1.49 fail.
> So I have add boost-system to the dependencyâs for guitarix.
> Maybe you didn't have it installed?
>
> greets
> hermann
Hello Hermann,
It wasn't installed. After installing it guitarix 0.23.1 builds fine.
Thanks! Looking forward to a weekend full of noodling :)
Jeremy
$ guitarix
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::erase
Aborted (core dumped)
After deleting .config/guitarix guitarix works again. I got this issue
when adding a LADSPA plugin. Tried doing it again:
(guitarix:26095): glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: basic_string::erase
Trace/breakpoint trap (core dumped)
Jeremy