Opened 14 years ago

Closed 14 years ago

#2285 closed Bugs (fixed)

Two segfaults

Reported by: Dave Abrahams Owned by: Ion Gaztañaga
Milestone: Boost 1.39.0 Component: interprocess
Version: Boost 1.35.0 Severity: Problem
Keywords: Cc:

Description

This is on Suse Linux Enterprise Server 10 with no updates. I've attached /etc/site-config.jam and the build log. The build command in libs/interprocess/test was:

~/bin/bjam -sHAVE_ICU=1 -sEXPAT_INCLUDE=/usr/include -sEXPAT_LIBPATH=/usr/lib64 --debug-configuration -j4 release --build-dir=/zorak/sles/build cxxflags=-Wno-non-virtual-dtor flat_tree_test iunordered_set_index_allocation_test -a

I can give you access to the system if you need to debug it.

Attachments (2)

site-config.jam (1.3 KB ) - added by Dave Abrahams 14 years ago.
Site Configuration
interprocess.log (11.0 KB ) - added by Dave Abrahams 14 years ago.
Build log

Download all attachments as: .zip

Change History (7)

by Dave Abrahams, 14 years ago

Attachment: site-config.jam added

Site Configuration

by Dave Abrahams, 14 years ago

Attachment: interprocess.log added

Build log

comment:1 by Ion Gaztañaga, 14 years ago

I've reproduced some release problems with latest GCC. Still no idea why. Thanks for the report.

comment:2 by Dave Abrahams, 14 years ago

More information: with the compiler I'm testing, it fails with

  • -Os
  • -O2
  • -O2 -fno-strength-reduce
  • and -O3

but not with -O1. This compiler is thought to have some optimization bugs, but if it's also failing with the latest GCC, I'm not sure who is to blame.

comment:3 by Dave Abrahams, 14 years ago

With my GCC-4.3.1, -Os ICEs the compiler and -O3 reproduces the crash.

With my GCC-4.2.3, both -Os and -O3 pass.

At least one bug report to the GCC team is in order.

comment:4 by Ion Gaztañaga, 14 years ago

Latest SVN code (that replaces some C casts with C++ new casts) is running fine on Mingw gcc 4.3.0 and variant=release. Can you confirm if your problem is also fixed?

comment:5 by Ion Gaztañaga, 14 years ago

Milestone: Boost 1.37.0Boost 1.39.0
Resolution: fixed
Status: newclosed

No more issues reported and tests seem fine. If the problem reappears, I'll reopen the bug.

Note: See TracTickets for help on using tickets.