Boost C++ Libraries: Ticket #977: bjam crashes when compiled with gcc 4.2

status, component changed; owner, version set

René Rivera — Wed, 23 May 2007 14:59:27 GMT

owner set to René Rivera
status new → assigned
version → Boost.Jam 3.1.14
component Building Boost → bjam

ismail@… — Wed, 30 May 2007 23:17:30 GMT

Any news on this one?

barner@… — Sat, 07 Jul 2007 21:53:54 GMT

Building bjam with -fno-strict-aliasing fixes this problem for me (on FreeBSD 7/amd64, gcc 4.2.0).

I will attach a patch that is based on http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=22;filename=boost.diff;att=1;bug=367825

attachment set

barner@… — Sat, 07 Jul 2007 21:55:44 GMT

attachment → patch-tools_jam_src_build.jam

Build bjam with -fno-strict-aliasing (fixes build with gcc 4.2.0)

ismail@… — Sat, 07 Jul 2007 22:43:46 GMT

Thats just a workaround, not a real fix, recently David Turner fixed ftjam for this bug. His changes could be backported.

René Rivera — Sat, 07 Jul 2007 23:34:48 GMT

Replying to ismail@pardus.org.tr:

Thats just a workaround, not a real fix, recently David Turner fixed ftjam for this bug. His changes could be backported.

Do you have a reference for the changes that fix it? I'd really like to fix this in bjam but I've had no luck in finding out what's going wrong.

ismail@… — Sat, 07 Jul 2007 23:46:24 GMT

http://david.freetype.org/jam/ftjam-2.5.3rc2.tar.bz2 is the fixed version as far as I know. For spesific changes you would have to ask David.

barner@… — Sun, 08 Jul 2007 09:27:00 GMT

One more data point:

g++42 (GCC) 4.2.1 20070627 (prerelease) does not exhibit this problem (tested on FreeBSD 6.2-STABLE/i386), while g++ (GCC) 4.2.0 20070514 [FreeBSD] (tested on FreeBSD 7.0/amd64) does.

Since the original reporter also spoke about g++ 4.2.0, the problem seems to related to the compiler version, and not to the CPU architecture. In the debian bug report mentioned above someone reports the problem is present on i386 (with g++ 4.2.0).

anonymous — Sun, 08 Jul 2007 09:36:39 GMT

Replying to barner@FreeBSD.org:

One more data point:

g++42 (GCC) 4.2.1 20070627 (prerelease) does not exhibit this problem (tested on FreeBSD 6.2-STABLE/i386), while g++ (GCC) 4.2.0 20070514 [FreeBSD] (tested on FreeBSD 7.0/amd64) does.

Nice one! I tried with gcc version 4.2.1 20070627 (prerelease) (Pardus Linux), I can't produce the bug either. So looks like its fixed for gcc 4.2.1.

Regards, ismail

bk@… — Tue, 24 Jul 2007 18:55:29 GMT

Hm, this bug seems to be quite odd to reproduce. It reproduces here with this gcc:

Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.2.1 --enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib64 --with-system-zlib --enable-shared --enable-cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --program-suffix=-4.2 --enable-version-specific-runtime-libs --without-system-libunwind --with-cpu=generic --host=x86_64-suse-linux Thread model: posix gcc version 4.2.1 20070705 (prerelease) (SUSE Linux)

Other architectures with equivalent gcc also fail: i386 ia64, ppc, ppc64, s390, s390x (no platform to which we have works)

Now the odd thing: It seems it worked with the same gcc version before, same sources, just in the previous rebuild of all openSUSE packages (I still try to verify this, as the boost-jam tarball has no testsuite, the segfault was not detected directly, only when trying to builld boost itself)

The main change in gcc42 before that was an update from suse-gcc-4_2-branch head (r126079) to suse-gcc-4_2-branch head (r126359)

glibc was changes to the lastest glibc-2.6 head, shortly before.

Anyway, we are applying the change regarding-fno-strict-aliasing in our builds.

If I'd have a vote, as that should not be a major performance isssue for jam, I'd just apply the workaround if you are not going to look for the real fix. Pity that you need yor own jam!

ismail@… — Mon, 30 Jul 2007 22:59:29 GMT

Bad news, I can reproduce the bug with gcc 4.2.1 and boost 1.34.1 :(

jrowe@… — Wed, 22 Aug 2007 13:19:53 GMT

I can also attest that gcc 4.2.1 and boost 1.34.1 produce this problem on a Sparc running Solaris 2.8. Adding -fno-strict-aliasing allows for success.

status changed; resolution set

René Rivera — Thu, 15 Nov 2007 18:39:13 GMT

status assigned → closed
resolution → fixed

Alternate version of the patch applied. Still wish I could find the real cause of the problem :-(

anonymous — Wed, 12 Mar 2008 14:49:05 GMT

This issue is still occurring for me with gcc 4.2.3 and boost 1.34.1 in Ubuntu. Using -fno-strict-aliasing fixed the problem. I thought it worth mentioning since apparently no recent gcc changes have cured the underlying problem, alas.

ysfwdtg — Fri, 03 Oct 2008 22:20:23 GMT

KFF8g4 <a href="http://hbapdhjrevdb.com/">hbapdhjrevdb</a>, [url=http://dnntzgtyxuyh.com/]dnntzgtyxuyh[/url], [link=http://tvmirclgmorn.com/]tvmirclgmorn[/link], http://azvamvfvjsgw.com/

Steven Watanabe — Sun, 04 Dec 2011 07:59:04 GMT

Replying to grafik:

Replying to ismail@pardus.org.tr:

Thats just a workaround, not a real fix, recently David Turner fixed ftjam for this bug. His changes could be backported.

Do you have a reference for the changes that fix it? I'd really like to fix this in bjam but I've had no luck in finding out what's going wrong.

I think the problem is casting to HASHDATA * *. I'll fix this properly soon.