8 Feb
2006
8 Feb
'06
1:49 p.m.
Chris Cannam wrote:
I think we need some more debug info, or a debugger
run, to find out why
MappedPluginSlot::~MappedPluginSlot is being called (if it is).
Which tools (ide/debugger) do you use?
But think I won't help here, as I have no idea, how to debug C programs
btw, is this build done with or without debug
information?
DEBUG_DSSI 1
DEBUG_DSSI_PROCESS 1
were set
Emanuel
8 Feb
8 Feb
2:16 p.m.
New subject: [linux-audio-dev] Re: [linux-audio-user] rosegarden dssi problem
Emanuel Rumpf wrote:
Chris Cannam wrote:
>I think we need some more debug info, or a debugger run, to find out why
>MappedPluginSlot::~MappedPluginSlot is being called (if it is).
>
>
>
I've added debug-output to MappedPluginSlot::~MappedPluginSlot
It is obviously being called:
RosegardenGUIDoc::xmlParse (reader.parse()): 90ms elapsed
~MappedPluginSlot() - MappedStudio.cpp
DSSIPluginInstance::~DSSIPluginInstance
DSSIPluginInstance::deactivate
dssi:/usr/local/lib/dssi/less_trivial_synth.so:LT S
DSSIPluginInstance::cleanup
dssi:/usr/local/lib/dssi/less_trivial_synth.so:LTS
DSSIPluginInstance::cleanup
dssi:/usr/local/lib/dssi/less_trivial_synth.so:LTS d one
it's called 2 times in the non-working output, but no-times in the
working output.
6686
days inactive
6686
days old
linux-audio-dev@lists.linuxaudio.org
1 comments
1 participants
participants (1)
-
Emanuel Rumpf