FS#49799 - [codeblocks] 16.01-3 is crashing
Attached to Project:
Community Packages
Opened by Mauro Santos (R00KIE) - Wednesday, 22 June 2016, 10:25 GMT
Last edited by Jelle van der Waa (jelly) - Thursday, 19 January 2017, 12:03 GMT
Opened by Mauro Santos (R00KIE) - Wednesday, 22 June 2016, 10:25 GMT
Last edited by Jelle van der Waa (jelly) - Thursday, 19 January 2017, 12:03 GMT
|
Details
Description:
Codeblocks 16.01-3 is crashing on startup with the following messages if started from a terminal: Warning: Mismatch between the program and library build versions detected. The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1009,wx containers,compatible with 2.6), and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1010,wx containers,compatible with 2.6). Starting Code::Blocks Release 16.01 rev 10692 Jun 11 2016, 23:37:16 - wx2.8.12 (Linux, unicode) - 64 bit Initialize EditColourSet ..... Initialize EditColourSet: done. This seems to point to the same problem described here [1]. The solution should be to recompile wxgtk2.8 (and maybe something else) with the same compiler version as used for codeblocks. I have tried to recompile wxgtk2.8 to confirm that would solve the problem but compiling wxgtk2.8 fails. Additional info: codeblocks 16.01-3 wxgtk2.8 2.8.12.1-4 Steps to reproduce: Start codeblocks from a terminal. It should crash on startup. [1] http://forums.codeblocks.org/index.php?topic=20872.0 |
This task depends upon
Closed by Jelle van der Waa (jelly)
Thursday, 19 January 2017, 12:03 GMT
Reason for closing: Fixed
Additional comments about closing: Applied a better fix in 16.01-8 which re-enables -O2 and stack fortification flags.
Thursday, 19 January 2017, 12:03 GMT
Reason for closing: Fixed
Additional comments about closing: Applied a better fix in 16.01-8 which re-enables -O2 and stack fortification flags.
Any more info about the crash?
I never get to see the main window, the only window that pops up is the debug report window.
[1] https://bbs.archlinux.org/viewtopic.php?id=214037
https://bugs.archlinux.org/task/49826?project=1
Bonus points if you also rebuild wxgtk 3 to make sure the gcc ABI matches the one you compiled codeblocks with.
Sooo... We still might have to path 2.8 to make things compatible. I'll see if I can brew a patch.
wxgtk2.8 does indeed compile with it. Trouble is, I can't seem to get past the linking part of the codeblocks build...
Build log for codeblocks withe the patched wxgtk2.8: http://pastebin.com/jUQtpsv5
My patch should not explain the codeblocks build failure.
Any ideas ? I think at that point, we could use a package maintainer point of view.
Still, even with both CB and wxgtk2.8 built with gcc6.1.1, codeblocks crash in the exact same way.
So, only way to run codeblocks at the moment is to recompile it against wxgtk 3 it seems. Shall we move this upstream ?
To build a working CodeBlocks, I changed one line in PKGBUILD. Change line "make" to "CXXFLAGS=-O1 CFLAGS=-O1 make".
Will try with different make flags first.
To work around this problem, build the program using makepkg along with such lines in makepkg.conf:
#CPPFLAGS=""
CFLAGS="-march=native -O0 -pipe -fstack-protector-strong --param=ssp-buffer-size=4"
CXXFLAGS="-march=native -O0 -pipe -fstack-protector-strong --param=ssp-buffer-size=4"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro"
Correctly must make a patch which eliminates govnokod "if (&strref == ((wxString*)NULL)) ...", associated with the wxPG_LABEL symbol.
Hopefully codeblocks will upgrade to wxgtk3 and also find a way to avoid similar problems to this in the future.
The updated codeblocks package will appear in [community] shortly. Please confirm that it is working correctly.
It seems to me better to remove the option -march=native of PKGBUILD file for ABS.
FS#50468,I highly suspect bad CFLAGS in PKGBUILD, innapropriate for some CPUs ( pentium dual core E6800 )
you can replace "-march=native" by "-mtune=generic" which is the default setting in /etc/makepkg.conf
Works here. Please confirm that it's working as it should.