Re: [Lmuse-user] [0.7.1pre2] crashes when loading ANY synth

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

ons 2004-12-15 klockan 13.00 skrev Sebastian Gutsfeld:
> Federico <xa...@in...> writes:
> 
> > i tried loading deicsonze and simpledrums.
> > i got twice SEGFAULT....
> >
> > i tried to backtrace one:
> > (P.S.: i am running slackware 10. i had to fix the std::string issue in
> > deicsonze, and add <iostream> to simpledrums)
> >
> > [...]
> 
> I only get a segmentation fault with simpledrums, all other synths work
> fine. I realized that this was caused by my Qt theme of choice:
> Highcolor. With Motif or Keramik theme there's no SEGFAULT. I also had
> to add the "-fno-rtti" optimization flag in the simpledrums makefile to
> get it working.
> 

Same problem here, only simpledrums crashes, on dlopen though. Many
problems with themes lately, it seems... :-/

So you had to both add -fno-rtti _and_ change theme? And it crashed
specifically when adding simpledrums? Or did the theme problem make MusE
crash before that?

> MusE also segfaults when changing the theme to Highcolor in the
> appearance settings.
> 

On startup?

> I use Debian testing with a 2.4.25 kernel lowlatency patched and
> CAP_SETPCAP enabled.
> 
> BTW, what does
> 
> ,----
> | set realtime scheduler: Operation not permitted
> `----
> 
> at startup mean? I run muse SUID enabled as normal user. This message
> doesn't come up when starting as root.
> 

I guess you don't have permission to give the midi thread realtime
priority. There's been talk about bugs in glibc when it comes to suid
and priorities. IIUIC, you should have the permission to give a thread
realtime priority when MusE is suid, but the bugs might make this
impossible. That's just what I've heard though, but it might explain why
it works when running as root. Actually, I've always had the same issue
here on my machine (old Mandrake 9.1) running as normal user. I think
Robert has experimented a bit with thread prioritiy initialization, but
I'm not sure if anything got into the CVS.. It's been up before though.

>    Sebastian
> 
> 
> PS: here is the backtrace from the simpledrums segmentation fault:
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 3395)]
> 0x40b9840d in __dynamic_cast () from /usr/lib/libstdc++.so.5
> (gdb) bt
> #0  0x40b9840d in __dynamic_cast () from /usr/lib/libstdc++.so.5
> #1  0x41327d6b in HighColorStyle::eventFilter ()
>    from /usr/lib/kde3/plugins/styles/highcolor.so
> #2  0x403b6e5e in QObject::activate_filters () from /usr/lib/libqt-mt.so.3
> #3  0x403b6d8c in QObject::event () from /usr/lib/libqt-mt.so.3
> #4  0x403ef60f in QWidget::event () from /usr/lib/libqt-mt.so.3
> #5  0x4035cbcf in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
> #6  0x4035c1ce in QApplication::notify () from /usr/lib/libqt-mt.so.3
> #7  0x080acb65 in MuseApplication::notify (this=0xbffff000, receiver=0xbfffdb20, 
>     event=0x885fe88) at app.cpp:1633
> #8  0x4035d9c6 in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3
> #9  0x403ee4b1 in QWidget::show () from /usr/lib/libqt-mt.so.3
> #10 0x403eeafd in QWidget::showChildren () from /usr/lib/libqt-mt.so.3
> #11 0x403ee5b7 in QWidget::show () from /usr/lib/libqt-mt.so.3
> #12 0x403eeafd in QWidget::showChildren () from /usr/lib/libqt-mt.so.3
> #13 0x403ee5b7 in QWidget::show () from /usr/lib/libqt-mt.so.3
> #14 0x40543d1c in QDialog::show () from /usr/lib/libqt-mt.so.3
> #15 0x417cfde6 in SimpleSynth::init (this=0x0, name=0xbfffdb20 "")
>     at simpledrums.cpp:800
> #16 0x417d1298 in instantiate (sr=48000, name=0xbfffdb20 "")
>     at simpledrums.cpp:1277
> #17 0x08067cbd in MessSynth::instantiate (this=0x85a07a0) at synth.cpp:197
> #18 0x08067ff1 in MessSynthIF::init (this=0x0, s=0xbfffdb20) at synth.cpp:229
> #19 0x0806808b in SynthI::initInstance (this=0x87d3b90, s=0x85a07a0, 
>     instanceName=@0xbfffe530) at synth.cpp:252
> #20 0x08067993 in createSynthI (sclass=@0xbfffe530) at synth.cpp:135
> #21 0x08068aa6 in Song::createSynthI (this=0x8455490, sclass=@0xbfffdb20)
>     at synth.cpp:375
> #22 0x080bd94c in MPConfig::addInstanceClicked (this=0xbfffdb20)
>     at confmport.cpp:332
> #23 0x080dfb58 in MPConfig::qt_invoke (this=0x85eef10, _id=54, _o=0xbfffe690)
>     at moc_confmport.cpp:101
> #24 0x403b952c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
> #25 0x403b9354 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
> #26 0x406fe28e in QButton::clicked () from /usr/lib/libqt-mt.so.3
> #27 0x4044b97a in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
> #28 0x403ef697 in QWidget::event () from /usr/lib/libqt-mt.so.3
> #29 0x4035cbcf in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
> #30 0x4035c2c4 in QApplication::notify () from /usr/lib/libqt-mt.so.3
> #31 0x080acb65 in MuseApplication::notify (this=0xbffff000, receiver=0xbfffdb20, 
>     event=0xbfffea50) at app.cpp:1633
> #32 0x402f1640 in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3
> #33 0x402ef2ce in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
> #34 0x403061a4 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
> #35 0x4036ef28 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
> #36 0x4036edd8 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
> #37 0x4035ce21 in QApplication::exec () from /usr/lib/libqt-mt.so.3
> #38 0x080a8dbe in main (argc=1, argv=0xbffff104) at app.cpp:1888
> 
> 

OK, HighColor definitely seems to be involved here... Hmm.... Thanks!

/Mathias