On Tue, 24 Feb 2009, Mark Allums wrote:

>> Use the .map files to track down exactly what function that dies (and then
>> you can objdump them to find the exact instruction). Then re-run gcc to do
>> assembly output (using -S -fverbose-asm perhaps) for the files with both
>> the old and the new gcc and compare the outputs. Hopefully that can offer
>> some clues.
>
> I will probably need some coaching here, as I am less experienced than I
> should be with the debugging side of things.

Sure, just start on this and ask if you get stuck on anything!

-- 
  / daniel.haxx.se