[2018-05-23 07:12:45 -1000] Gaetan Bisson:
> [2018-05-23 10:28:52 -0300] Thiago Macieira:
> > On Wednesday, 23 May 2018 05:08:58 -03 Gaetan Bisson wrote:
> > > Any ideas how to debug this?
> >
> > Can you valgrind? Without debug symbols in Qt it may be a little difficult
> > to
> > make sense of what we're seeing, but it might help.
>
> Sure; see valgrind's log attached. The core dump is too big to send by
> email but I can find a way to get it to you if needed. Also, while I was
> asleep, Arch's Qt packager bisected the faulty commit to:
>
>
> http://code.qt.io/cgit/qt/qtbase.git/patch/?id=1c0fcbc887459d8963088309e83303eb1a7d2db0
>
> Which I note is also suspected for other segfaults:
>
> https://github.com/lxqt/libfm-qt/issues/164
>
> He has reported this issue there:
>
> https://bugreports.qt.io/browse/QTBUG-68427
Oh, it's also there:
https://bugreports.qt.io/browse/QTBUG-67948
Cheers.
--
Gaetan
_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
