[Clam-devel] Re: bug: SMSTools crashes at loading (last svn)
greg.kellum at gmail.com
Tue Sep 11 07:09:07 PDT 2007
Did you fix the problem with SMSTools yourself already? I haven't been able
to reproduce the problem. I did a clean check-out of the entire clam
repository and recompiled everything, but SMSTools starts without problems.
For some strange reason though, it's not letting me view the spectogram
after an analysis...
On 9/5/07, Greg Kellum <greg.kellum at gmail.com> wrote:
> Hi Pau,
> Yes, that could very well be due to changes that I made. Um... I brought
> my old PowerPC Mac to the MTG today, and as I told you, I can't run CLAM on
> it. But I'll take a look at the problem tomorrow when I have my Intel Mac.
> We should talk about SMSTools sometime. I've been thinking about whether
> it would be a good idea to integrate my loopMaker code into SMSTools. And
> I'd like to talk to you about this and some other ideas that I have for the
> On 9/5/07, Pau Arumi <parumi at iua.upf.edu> wrote:
> > SMSTools crashes with a mysterious (to me) segmentation fault when
> > loading.
> > The gdb trace shows it's in the SDIFIn configure from the
> > constructor. Strangely, the crash happens when accessing the
> > composite list.
> > Greg, does it rings some bell on you? is maybe related to SDIF
> > refactorings for the real-time synthesizer?
> > Filed bug #305 on the tracker.
> > Pau
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread -1254275376 (LWP 8594)]
> > 0xb76185a2 in CLAM::ProcessingComposite::Insert (this=0xb7675a40,
> > obj=@0x839b3c4) at scons/libs/core/src/ProcessingComposite.cxx:76
> > 76 if((*it)==&obj) return;
> > (gdb) bt
> > #0 0xb76185a2 in CLAM::ProcessingComposite::Insert
> > (this=0xb7675a40, obj=@0x839b3c4) at
> > scons/libs/core/src/ProcessingComposite.cxx:76
> > #1 0xb761f133 in CLAM::Processing::Configure (this=0x839b3c4,
> > c=@0xbfaee824) at scons/libs/core/src/Processing.cxx:115
> > #2 0xb707407a in SDIFIn (this=0x839b3c4) at
> > scons/libs/processing/src/SDIFIn.cxx:48
> > #3 0x0820f9d6 in SDIFSerializer (this=0x839b3c0) at
> > src/SDIFSerializer.cxx:32
> > #4 0x0820ed6f in SerializationController (this=0x839b3b8) at
> > src/SerializationController.cxx:28
> > #5 0x081cd99b in SMSBase (this=0x839b380) at src/SMSBase.cxx:55
> > #6 0x08168766 in Engine (this=0x839b380) at
> > src/QtImpl/System/Engine.cxx:21
> > #7 0x08168814 in QtSMS::Engine::Instance () at
> > src/QtImpl/System/Engine.cxx:16
> > #8 0x081c51ed in QtSMS::QtSMSTools::InitSMSTools (this=0x836a478)
> > at src/QtImpl/Application/QtSMSTools.cxx:45
> > #9 0x081c5650 in QtSMSTools (this=0x836a478) at
> > src/QtImpl/Application/QtSMSTools.cxx:33
> > #10 0x08233e91 in main (argc=1, argv=0xbfaeea94) at
> > src/QtImpl/main.cxx:35
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the clam-devel