Beta binary

[Tomaz Canabrava]

can you delete the AtmospherePlugin from the folder to see if marble will
launch?
we are not using it, anyhow.


On Thu, Nov 28, 2013 at 8:40 AM, Lubomir I. Ivanov <neolit123 at gmail.com>wrote:

> On 28 November 2013 12:04, Robert Helling <helling at lmu.de> wrote:
> > Hi,
> >
> > I just tried to run the binary for 3.9.BETA supplied on the downloads
> section of the web page. First, it seems to be unsigned (so for my settings
> it complains until explicitly enabled in the system preferences and then it
> crashes on startup (different from previous crashes due to the proxy
> problem or the other marble problem it doesn’t even get as far as opening
> the window).
> >
> > Crash report below.
> >
> > Best
> > Robert
> >
> > Process:         subsurface [90909]
> > Path:            /Volumes/VOLUME/Subsurface.app/Contents/MacOS/subsurface
> > Identifier:      org.hohndel.subsurface
> > Version:         3.9
> > Code Type:       X86-64 (Native)
> > Parent Process:  launchd [182]
> > Responsible:     subsurface [90909]
> > User ID:         501
> >
> > Date/Time:       2013-11-28 11:04:09.873 +0100
> > OS Version:      Mac OS X 10.9 (13A603)
> > Report Version:  11
> > Anonymous UUID:  4843FA46-C37F-26A1-24A5-735D27A4A400
> >
> >
> > Crashed Thread:  0  Dispatch queue: com.apple.main-thread
> >
> > Exception Type:  EXC_CRASH (SIGABRT)
> > Exception Codes: 0x0000000000000000, 0x0000000000000000
> >
> > Application Specific Information:
> > abort() called
> >
> > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> > 0   libsystem_kernel.dylib              0x00007fff8d5a0866
> __pthread_kill + 10
> > 1   libsystem_pthread.dylib             0x00007fff92a6f35c pthread_kill
> + 92
> > 2   libsystem_c.dylib                   0x00007fff8c675bba abort + 125
> > 3   QtCore                              0x000000010b8e1a5b
> qt_message_output(QtMsgType, char const*) + 200
> > 4   QtCore                              0x000000010b8e1bef
> qt_message(QtMsgType, char const*, __va_list_tag*) + 203
> > 5   QtCore                              0x000000010b8e165f qFatal(char
> const*, ...) + 149
> > 6   QtGui                               0x000000010bcb80c8
> qt_pixmap_thread_test() + 111
> > 7   QtGui                               0x000000010bcb7ffe
> QPixmap::QPixmap() + 42
> > 8   libAtmospherePlugin.so              0x00000001094e3cd0
> Marble::AtmospherePlugin::AtmospherePlugin() + 80 (AtmospherePlugin.cpp:30)
> > 9   libAtmospherePlugin.so              0x00000001094e3c75
> Marble::AtmospherePlugin::AtmospherePlugin() + 21 (AtmospherePlugin.cpp:31)
> > 10  libAtmospherePlugin.so              0x00000001094e54f4
> qt_plugin_instance + 164 (AtmospherePlugin.cpp:192)
>
>
> what is the console output before the crash (if there is)?
>
> if this is up to date:
>
> http://api.kde.org/4.x-api/kdeedu-apidocs/marble/html/AtmospherePlugin_8cpp_source.html
>
> the only place i find QPixmap interaction is here:
>
> 167  int diameter = (int) ( 2.1 * (qreal) ( viewParams->radius()));
> 168  m_renderPixmap = QPixmap(diameter, diameter);
>
> well, this could be a bad diameter value for the globe, but i somehow
> doubt it. do we have control of the globe radius via the API?
> other than that, i really think this crash dump should be show to the
> marble developers...
>
> lubomir
> --
> _______________________________________________
> subsurface mailing list
> subsurface at hohndel.org
> http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hohndel.org/pipermail/subsurface/attachments/20131128/f4179e88/attachment.html>