Am Mittwoch, 20. Juni 2018, 22:15:27 CEST schrieb Thiago Macieira: > On Wednesday, 20 June 2018 12:35:45 PDT Martin Gysel wrote: > > I get the following backtrace: > > > > QPainter::begin: Paint device returned engine == 0, type: 2 > > Thanks Martin. > > I don't see anything in the backtrace belonging to Subsurface, so this > appears to be a regular Qt regression. Turns out there were a lot of > changes to QHeaderView earlier this year, so one of the must be at fault. I > can't spot which one just by looking though. > > To help constrain the search, do you know if this warning was printed with > Qt 5.10 too?
I switch from 5.9.x to 5.11, so I don't know > > > #3 0x00007ffff2724f74 in QPainter::begin(QPaintDevice*) () from > > /usr/lib64/libQt5Gui.so.5 > > #4 0x00007ffff3551777 in () from /usr/lib64/libQt5Widgets.so.5 > > #5 0x00007ffff3551c0c in QHeaderView::mousePressEvent(QMouseEvent*) () > > from /usr/lib64/libQt5Widgets.so.5 > > I'm trying to guess which frame is that ??, but it's not clear what it is. > My first guess was QHeaderViewPrivate::setupSectionIndicator, which does > have a QPainter, but that function is painting on a QPixmap and that > wouldn't have printed the warning. But that leaves me out of options. > > Can you install the debug symbols for the library? > > zypper in libQt5Gui5-debuginfo > > That should resolve the ?? to something useful, and possibly also give us > line numbers. I this still needed after the backtrace from Dietrich? If so I can compile 5.11.1 with debug symbols (I'm on gentoo) > > PS: I'm experimenting with an optimised build of Qt5 that you can find at > https://build.opensuse.org/package/show/ > home:thiagomacieira:branches:openSUSE:Factory/libqt5-qtbase is there any related patch included I should try? /martin
_______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
