On Sun, Jan 4, 2015, at 01:09 AM, Stuart Henderson wrote: > On 2014/12/25 21:28, Adam Wolk wrote: > > 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() > > These are api warnings from the linker, unfortunately fairly common to > trigger them when porting software, they're mostly helpful for people > using OpenBSD as a dev platform (and as a bit of a warning to porters > that > some things might be worse than usual ;) > Just reporting what I see. Worse then usual? I prefer to know that something potentially isn't working as expected so happy to be notified by OpenBSD about it :)
> > 3. Crash on first run > > > > On first run I see the browser window rendered and a second later I hit > > the following crash > > > > $ ./otter-browser > > ./otter-browser:/usr/local/lib/libestdc++.so.16.0: > > /usr/lib/libstdc++.so.57.0 : WARNING: > > symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your > > program > > Some ports are compiled with g++ 4.8 rather than the default 4.2.1 from > the base os (last GPLv2 version), so mixing c++ libraries. It's not ideal > but in practice hasn't caused problems. As far as Otter goes I think > building with 4.8 would be a good idea, if you're doing this within > the ports framework, something like the below in the Makefile will set > it up: > > MODULES += gcc4 > MODGCC4_ARCHS = * > MODGCC4_LANGS = c++ > I didn't dive into the porting framework yet. I wanted to start of with a plain build outside of ports. But thank you for this insight - I will try switching out the compiler for this one. > > Warning: QGtkStyle could not resolve GTK. Make sure you have installed > > the proper libraries. > > (/usr/obj/ports/qt-everywhere-opensource-src-5.3.2/qt-everywhere-opensource-src-5.3.2/qtbase/src/widgets/styles/qgtkstyle_p.cpp:583, > > virtual void QGtkStylePrivate::initGtkWidgets() const) > > otter-browser(20064) in free(): error: bogus pointer (double free?) > > 0xdfdfdfdf > > Abort trap (core dumped) > > Most likely a use-after-free; we have some malloc hardening on by > default. > See malloc.conf(5) about 0xdf. > Yep, it definitely looks like it. cschutijser@ mentioned in my opinion the same bug that he reported upstream (https://bugreports.qt-project.org/browse/QTBUG-43623). That stack trace does match what I see so I consider it a problem in Qt itself. I don't think I want to tweak malloc.conf for Otter. I would prefer to put more pressure on the Qt folk :)
