[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#794406: g++: Non-deterministic "/usr/include/c++/5/bits/basic_string.h:121:53: internal compiler error: Segmentation fault" when compiling aptitude 0.7-1



On 08/02/2015 09:59 PM, Axel Beckert wrote:
> Hi Matthias,
> 
> Matthias Klose wrote:
>> Control: reassign -1 g++-5
>> Control: found -1 5.2.1-14
> 
> Oops, sorry for that mistake.
> 
>>> I've just tried to build the upcoming aptitude 0.7-1 inside a pbuilder
>>> chroot.
>>>
>>> I've first recompiled the following source packages with gcc-5/5.2.1-14
>>> respectively g++-5/5.2.1-14 and against libstdc++6/5.2.1-14 and
>>> installed the (necessary) packages built that way:
>>
>>> Please submit a full bug report,
>>> with preprocessed source if appropriate.
>>> Please include the complete backtrace with any bug report.
>>> See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
>>> The bug is not reproducible, so it is likely a hardware or OS problem.
>>
>> I haven't see this before;
> 
> I ran into it only once, and unfortunately couldn't reproduce it
> afterwards anymore, e.g. worked fine under gdb.
> 
>> just pointing out that the build fails later in a
>> "consistent" way (https://launchpad.net/ubuntu/+source/aptitude):
> 
> *sigh* That's irrelevant as it's 0.6.11 (or rather
> 0.6.11ubuntuSomething). I talk about the to be uploaded 0.7 (see also
> the subject) _with_ gcc5/C++11 fixes:
> https://anonscm.debian.org/cgit/aptitude/aptitude.git/log/?id=refs/heads/debian-sid

ok, both locally and on the Ubuntu buildds in a wily environment, I get another
build failure.

  https://launchpad.net/~doko/+archive/ubuntu/toolchain/+packages

however, this is with a rebuilt boost1.58, libsigc++2.0, libapt-pkg-dev,
xapian-core, cppunit.

xapian and boost were uploaded today, bug reports for libsigc++ and cppunit
exist (if maintainers don't reply, maybe you could coordinate these
transitions?). Michael Vogt provided me with an update for apt which I should
upload, coordinating with David.

So I think unstable is not yet ready to do this rebuild.

Matthias


Reply to: