I seem to be the only one getting this, and I don't get it reliably
either. It seems to be timing-related somehow, because it never
happens under gdb, but I *can* catch it with a core-dump and then get
gdb to show me where it is. Backtrace appended in case it makes
anybody go "yeah".
This may be b
On 13 June 2017 at 13:09, Linus Torvalds wrote:
> #14 0x7fa0764abe8b in Marble::MarbleModel::setMapThemeId(QString
> const&) () from
> /home/torvalds/src/install-root/lib/libssrfmarblewidget.so.21
looks very similar to a recent setMapThemId() related breakage that
was caused by concurrency p
On terça-feira, 13 de junho de 2017 03:09:51 PDT Linus Torvalds wrote:
> I seem to be the only one getting this, and I don't get it reliably
> either. It seems to be timing-related somehow, because it never
> happens under gdb, but I *can* catch it with a core-dump and then get
> gdb to show me whe
On 13 June 2017 at 17:08, Thiago Macieira wrote:
> On terça-feira, 13 de junho de 2017 03:09:51 PDT Linus Torvalds wrote:
>> I seem to be the only one getting this, and I don't get it reliably
>> either. It seems to be timing-related somehow, because it never
>> happens under gdb, but I *can* catc
On terça-feira, 13 de junho de 2017 07:54:14 PDT Lubomir I. Ivanov wrote:
> looks like we didn't add the QLoggingCategory after that discussion:
> http://lists.subsurface-divelog.org/pipermail/subsurface/2017-April/028321.h
> tml
>
> in the end i did not understand how to modify the MarbleDebug.cp
