2014-12-26 2:33 GMT+03:00 Adam Wolk <adam.w...@koparo.com>: > On Fri, Dec 26, 2014, at 12:15 AM, Vadim Zhukov wrote: >> >> Yes, known problem. CMake config file for Qt5Sql talks about all >> backends always. To be redone after fixing other urgent stuff. >> >> BTW, can't the Otter use the SQLite3 backend instead of SQLite2? The >> former is bundled with Qt5 itself because SQLite3 is part of base >> system nowadays. >> > > I installed the sqlite2 backend as that's the only one that showed up > on packages for me: > > $ pkg_info -Q qt5 > qt5-5.3.2p0 (installed) > qt5-examples-5.3.2 > qt5-mysql-5.3.2 (installed) > qt5-postgresql-5.3.2 (installed) > qt5-sqlite2-5.3.2 (installed) > qt5-tds-5.3.2 (installed) > > that's the complete list of qt5 packages I get for this query. > >> > 2. gcc warnings after compilation >> > Linking CXX executable otter-browser >> > /usr/local/lib/qt5/libQt5Script.so.0.0: warning: random() may return >> > deterministic values, is that what you want? >> > /usr/local/lib/qt5/libQt5WebKit.so.0.0: warning: strcpy() is almost >> > always misused, please use strlcpy() >> > /usr/local/lib/qt5/libQt5Core.so.0.0: warning: rand() may return >> > deterministic values, is that what you want? >> > /usr/local/lib/qt5/libQt5Script.so.0.0: warning: sprintf() is often >> > misused, please use snprintf() >> > /usr/X11R6/lib/libX11.so.16.0: warning: strcat() is almost always >> > misused, please use strlcat() >> > /usr/local/lib/libglib-2.0.so.4200.0: warning: stpcpy() is dangerous; do >> > not use it >> > /usr/local/lib/libglib-2.0.so.4200.0: warning: vsprintf() is often >> > misused, please use vsnprintf() >> >> That's "normal"... Well, except strcpy() in Qt5WebKit - strange, I >> thought I removed them all. I'll check again, thanks for reporting. >> The sprintf() worths looking into as well. >> >> (other points to be answered in a separate mail) >> >> -- >> Vadim Zhukov >> > > First of all thanks for the reply. I'm trying my best to help out and I > hope I'm not spamming. > If I should remove the CC to KDE porters then please inform me.
No, no, no, everyting is normal. The reality is that I'm 95% of "KDE development team" as of now, and also I'm responsible for Qt5 as well. The "KDE team" is just my hope that someone will pick up my work when I'll be hit by bus. :) > Here are some follow ups that I found after investigating more since my > last email. > > 1. The double free crashes happen in 2 cases. > a) trying to resize the window > b) closing a modal dialog > > 2. While debugging one of the core dumps with gdb - gdb core dumped > itself > I have this core dump set aside in case it's meaningful to someone. GDB can't debug real Qt5 apps. :( That comes from old binutils here in OpenBSD, at least, and that's not a thing I can fix, sorry. > 3. The browser itself works. I can load pages (ie. openbsd.org) open > tabs, close tabs etc. > > Here are the backtraces: > > 1) GDB core dump while debugging a core dump (this is while trying to > resize the whole window) > #0 0x04a7e371 in kill () at <stdin>:2 > 2 <stdin>: No such file or directory. > in <stdin> > (gdb) bt > #0 0x04a7e371 in kill () at <stdin>:2 > #1 0x04abc836 in raise (s=6) at /usr/src/lib/libc/gen/raise.c:39 > #2 0x04abc780 in abort () at /usr/src/lib/libc/stdlib/abort.c:53 > #3 0x04ab8b87 in wrterror (msg=0x24a16956 "bogus pointer (double > free?)", p=0xdfdfdfdf) at /usr/src/lib/libc/stdlib/malloc.c:281 > #4 0x04aba099 in free (ptr=0xdfdfdfdf) at > /usr/src/lib/libc/stdlib/malloc.c:1282 > #5 0x0fa1c516 in QXcbShmImage::destroy () from > /usr/local/lib/qt5/plugins/platforms/libqxcb.so > #6 0xdfdfdfdf in ?? () > #7 0x0000027f in ?? () > #8 0x2f478040 in QCoreApplicationPrivate::checkInstance(char > const*)::__PRETTY_FUNCTION__ () from > /usr/local/lib/qt5/libQt5Core.so.0.0 > #9 0x2a80b704 in ?? () from /usr/lib/libstdc++.so.57.0 > #10 0x82f09740 in ?? () > #11 0x2fa07b48 in ?? () from > /usr/local/lib/qt5/plugins/platforms/libqxcb.so > #12 0x8561f630 in ?? () > #13 0x0fa1d4ac in QXcbBackingStore::resize () from > /usr/local/lib/qt5/plugins/platforms/libqxcb.so > #14 0x0145dca2 in QBackingStore::resize () from > /usr/local/lib/qt5/libQt5Gui.so.0.0 > #15 0x04fdf74c in QWidgetBackingStore::doSync () from > /usr/local/lib/qt5/libQt5Widgets.so.0.0 > #16 0x04fe083e in QWidgetBackingStore::sync () from > /usr/local/lib/qt5/libQt5Widgets.so.0.0 > Segmentation fault (core dumped) > > 2) backtrace from dialog close > #0 0x0e212371 in kill () at <stdin>:2 > 2 <stdin>: No such file or directory. > in <stdin> > (gdb) bt > #0 0x0e212371 in kill () at <stdin>:2 > #1 0x0e250836 in raise (s=6) at /usr/src/lib/libc/gen/raise.c:39 > #2 0x0e250780 in abort () at /usr/src/lib/libc/stdlib/abort.c:53 > #3 0x0e24cb87 in wrterror (msg=0x2e1aa956 "bogus pointer (double > free?)", p=0xdfdfdfdf) at /usr/src/lib/libc/stdlib/malloc.c:281 > #4 0x0e24e099 in free (ptr=0xdfdfdfdf) at > /usr/src/lib/libc/stdlib/malloc.c:1282 > #5 0x0ac88516 in QXcbShmImage::destroy () from > /usr/local/lib/qt5/plugins/platforms/libqxcb.so > #6 0xdfdfdfdf in ?? () > #7 0x852d7600 in ?? () > #8 0xcfbd7cc4 in ?? () > #9 0x0e24e0b5 in free (ptr=0x873cf990) at > /usr/src/lib/libc/stdlib/malloc.c:1285 > #10 0x0babb7a9 in QWidget::~QWidget () from > /usr/local/lib/qt5/libQt5Widgets.so.0.0 > #11 0x0bcba297 in QDialog::~QDialog () from > /usr/local/lib/qt5/libQt5Widgets.so.0.0 > #12 0x1910c16d in Otter::StartupDialog::~StartupDialog () from > /home/mulander/otter-head/otter/build/otter-browser > #13 0x18fd91d3 in main () from > /home/mulander/otter-head/otter/build/otter-browser > Current language: auto; currently asm I have another report about bugs in Qt5WebKit. It's New Year coming here in Russia; hope to have time to debug those things during holidays. I understand those crashes are not pretty looking, but there is some other urgent stuff in Qt land as well. :-\ -- WBR, Vadim Zhukov
