Beta binary

[Lubomir I. Ivanov]

On 28 November 2013 20:48, Linus Torvalds <torvalds at linux-foundation.org> wrote:
> Btw, there seems to be something screwy with marble on Linux too. I
> just got a couple of non-reproducible SIGSEGV's with current
> subsurface (while testing the temperature thing):
>
>   Thread (pooled)[27180]: segfault at 30 ip 0000003a3a2f1020 sp
> 00007f128effca38 error 4 in
> libmarblewidget.so.0.16.2[3a3a000000+487000]
>   Thread (pooled)[27181]: segfault at 30 ip 0000003a3a2f1020 sp
> 00007f128e7fba38 error 4 in
> libmarblewidget.so.0.16.2[3a3a000000+487000]
>   Thread (pooled)[27215]: segfault at 30 ip 0000003a3a2f1020 sp
> 00007f2883ffea38 error 4 in
> libmarblewidget.so.0.16.2[3a3a000000+487000]
>   Thread (pooled)[27249]: segfault at 30 ip 0000003a3a2f1020 sp
> 00007f7f596c2a38 error 4 in
> libmarblewidget.so.0.16.2[3a3a000000+487000]
>   Thread (pooled)[27301]: segfault at 30 ip 0000003a3a2f1020 sp
> 00007ff21cff8a38 error 4 in
> libmarblewidget.so.0.16.2[3a3a000000+487000]
>
> but they went away when I tried to run it under gdb.
>
> I suspect we need to start running valgrind again..
>

just looking at that makes me question marble again.
actually it seems to be most stable on windows - never had any issues
apart from paths.

the above issue that robert posted is plain odd for osx.
i seriously think that we need to start spamming them with some reports...

lubomir
--