OK, I found it. I had to move the "id" attribute from the application tag
to the extension, like here:

http://mitk.org/git/?p=MITK.git;a=blobdiff;f=Plugins/org.mitk.gui.qt.coreapplication/plugin.xml;h=45d39593a22bf2cf2de61912694b5101136b4ed7;hp=5c63c195463a82b7f0202d9bbd067b7f40f025e9;hb=4be8adcd4d4ce2d541b2f3b36b9f5559a9e5c27d;hpb=e7f83bacdaa2d2eefa916a3aed82495e2ae8d006

By the way, what is the products extension point for?

Cheers,
Miklos


On 14 July 2015 at 18:12, Sascha Zelzer <s.zel...@dkfz-heidelberg.de> wrote:

>  Hi Miklos,
>
> the stack trace suggests that the segfault happens during shutdown of the
> CTK plugin framework. The question is, why is it shutting down?
>
> Could you provide a "real" stack trace (using the debugger) and the
> console output with --BlueBerry.consoleLog ?
>
> Thanks,
> Sascha
>
> On 07/13/2015 07:52 PM, Miklos Espak wrote:
>
> Hi,
>
>  we have upgraded to MITK 2015.05.0. The code compiles, but our app
> segfaults at start.
>
>  Any clue what the problem can be?
>
>  The stack trace:
>
>  0 ctkPluginContextPrivate::isPluginContextValid ctkPluginContext.cpp 42
> 0x7ffff5cf0cf2
> 1 ctkPluginContext::getServiceReferences ctkPluginContext.cpp 142
> 0x7ffff5cf160c
> 2 ctkPluginContext::getServiceReferences<ctkApplicationHandle>
> ctkPluginContext.h 324 0x7fffeafe63bd
> 3 berry::ApplicationContainer::StopAllApps berryApplicationContainer.cpp
> 490 0x7fffeafe188c
> 4 berry::ApplicationContainer::PluginChanged berryApplicationContainer.cpp
> 484 0x7fffeafe17ee
> 5 berry::ApplicationContainer::qt_static_metacall
> moc_berryApplicationContainer.cxx 49 0x7fffeb06e7f9
> 6 QMetaObject::activate(QObject*, QMetaObject const*, int, void**)
> /build/opt/qt-4.8.7/lib/libQtCore.so.4 0x7ffff7a82cea
> 7 ctkPluginFrameworkListeners::pluginChangedDirect
> moc_ctkPluginFrameworkListeners_p.cxx 109 0x7ffff5d4ea86
> 8 ctkPluginFrameworkListeners::emitPluginChanged
> ctkPluginFrameworkListeners.cpp 174 0x7ffff5d12720
> 9 ctkPluginFrameworkPrivate::shutdown0 ctkPluginFramework_p.cpp 178
> 0x7ffff5d17f93
> 10 QtConcurrent::VoidStoredMemberFunctionPointerCall2<void,
> ctkPluginFrameworkPrivate, bool, bool, bool, bool>::runFunctor
> qtconcurrentstoredfunctioncall.h 615 0x7ffff5d1b8a8
> 11 QtConcurrent::RunFunctionTask<void>::run qtconcurrentrunbase.h 134
> 0x7ffff5d18ecf
> 12 ?? /build/opt/qt-4.8.7/lib/libQtCore.so.4 0x7ffff796072e
> 13 ?? /build/opt/qt-4.8.7/lib/libQtCore.so.4 0x7ffff796c7ef
> 14 start_thread 312 0x7ffff6bba182
> 15 clone 111 0x7ffff6eca47d
>
>
>  In (2) "clazz" is "org.commontk.service.application.ApplicationHandle",
> "filter" is "(!(application.state=STOPPING))"
>
>
>  I guess it is related to the new application launcher mechanism.
>
>  Our main function looks like this:
>
>  int main(int argc, char** argv)
>
> {
>
>   // Create a QApplication instance first
>
>   mitk::BaseApplication app(argc, argv);
>
>   app.setApplicationName("NiftyView");
>
>   app.setOrganizationName("CMIC");
>
>    // Preload the org.mitk.gui.qt.common plug-in (and hence also Qmitk) to 
> speed
>
>   // up a clean-cache start. This also works around bugs!
>   in older gcc and glibc implementations,
>
>   // which have difficulties with multiple dynamic opening and closing of 
> shared libraries with
>
>   // many global static initializers. It also helps if dependent <
> /span>libraries have weird static
>
>   // initialization methods and/or missing de-initialization code.
>
>   QStringList preloadLibs;
>
>   preloadLibs << "liborg_mitk_gui_qt_common";
>
>   app.setPreloadLibraries(preloadLibs);
>
>    app.setProperty(mitk::BaseApplication::PROP_APPLICATION, 
> "uk.ac.ucl.cmic.gui.qt.niftyview");
>
>    return app.run();
>
> }
>
>
>  Cheers,
> Miklos
>
>
>
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> mitk-users mailing list
> mitk-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mitk-users
>
>
------------------------------------------------------------------------------
_______________________________________________
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to