Chris Cannam wrote:
>On Wednesday 08 Feb 2006 19:17, Emanuel Rumpf wrote:
>
>
>>I've added debug-output to MappedPluginSlot::~MappedPluginSlot
>>[...]
>>it's called 2 times in the non-working output, but no-times in the
>>working output.
>>
>>
>
>Any chance you can get a stack trace of where it's called? One way to do this
>would be to add the line
>
>assert(0);
>
>
This had no effect.
>at the top of MappedPluginSlot::~MappedPluginSlot(). That should cause a
>crash in the sequencer process and (probably) show the KDE debug window with
>a stack trace in it when the crash happens. That won't tell us the whole
>story, because the stack trace will only be for the sequencer process (it
>won't indicate what the GUI process tried to get the sequencer to do) but it
>should get us somewhere...
>
>Of course, this will only work if MappedPluginSlot::~MappedPluginSlot() is
>never called except in the "incorrect" situation. I just added an assert(0)
>call to the function in my copy, and I found that the call never seems to be
>reached in normal use, so I think this should be a safe assumption.
>
>
>
Received on Thu Feb 9 20:15:05 2006
This archive was generated by hypermail 2.1.8 : Thu Feb 09 2006 - 20:15:05 EET