On Saturday 11 July 2015 19:28:42 Tomaz Canabrava wrote: > On Sat, Jul 11, 2015 at 7:00 PM, Linus Torvalds < > > torva...@linux-foundation.org> wrote: > > #0 0x00007fffefa67a98 in raise () at /lib64/libc.so.6 > > #1 0x00007fffefa6972a in abort () at /lib64/libc.so.6 > > #2 0x00007fffefaaaea2 in () at /lib64/libc.so.6 > > #3 0x00007fffefab3ef8 in _int_malloc () at /lib64/libc.so.6 > > #4 0x00007fffefab6b5e in malloc () at /lib64/libc.so.6 > > #5 0x00007ffff042d453 in QArrayData::allocate(unsigned long, unsigned > > long, unsigned long, QFlags<QArrayData::AllocationOption>) () at > > /lib64/libQt5Core.so.5 > > #6 0x00007ffff04b9b1f in QString::QString(int, QChar) () at > > /lib64/libQt5Core.so.5 > > #7 0x00007ffff04978f7 in QLocalePrivate::dateTimeToString(QString > > const&, QDateTime const&, QDate const&, QTime const&, QLocale const*) > > const () at /lib64/libQt5Core.so.5
> This crash is not related to subsurface but to Qt, I'm not sure what > happened there but did you updated your Qt and didn`t compiled Subsurface > after update? > The #13 0x00007ffff1693668 in QDateTimeEdit::setTime(QTime const&) () line > tells me that this Qt fault, we are passing a stack variable to a > QDateTime and it`s getting corrupted inside an internal impelmentation of > QArrayData > > Thiago? It crashed inside malloc, so the problem is not in the stack trace. Something corrupted the malloc structures. Valgrind would have been the best, but didn't work... -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface