Re: PATCH RFA: Add -static-libstdc++ option to g++

[Dave Korn <dave dot korn dot cygwin at googlemail dot com>]

NightStrike wrote:

>> This patch looks like it was committed here:
>>
>> http://gcc.gnu.org/ml/gcc-cvs/2009-06/msg00935.html
>>
>> That was revision 148951.
>>
>> That revision breaks the linux64 to win64 cross compiler for g++.  Any
>> attempt to use g++ results in output like this:
>>
>> *** glibc detected *** malloc(): memory corruption (fast):
>> 0x00000000005412c0 ***
>> *** glibc detected *** malloc(): memory corruption (fast):
>> 0x00000000005412a0 ***
>> *** glibc detected *** corrupted double-linked list: 0x00000000005412b0 ***
>> *** glibc detected *** malloc(): memory corruption (fast):
>> 0x00000000005412c0 ***
>> *** glibc detected *** malloc(): memory corruption (fast):
>> 0x00000000005412a0 ***
>> *** glibc detected *** corrupted double-linked list: 0x00000000005412c0 ***
>> *** glibc detected *** malloc(): memory corruption (fast):
>> 0x00000000005412b0 ***
>> *** glibc detected *** malloc(): memory corruption (fast):
>> 0x00000000005412b0 ***
>> *** glibc detected *** corrupted double-linked list: 0x00000000005412c0 ***
>> libtool.m4: error: problem compiling CXX test program
>> *** glibc detected *** malloc(): memory corruption (fast):
>> 0x00000000005412b0 ***
>>
> 
> Ping

  The most plausible explanation is that there's an off-by-one error of some
sort in the bit where it's rewriting the argv array.  If you felt like
catching it under GDB and stepping through lang_specific_driver() in
cp/g++spec.c to see what's going wrong, you could probably expedite the
resolution of this problem.  Filing a PR might help keep it from getting
overlooked too and would provide a good place to record your observations from
debugging.

    cheers,
      DaveK