Re: [trinity-devel] kwrite Crash - Now Down To 3/29 -> 4/1 (this may not be good -- gcc to blame?)

On 3 May 2012, Timothy Pearson told this:

                                    As ugly as it may be, we may need

to entertain the notion that gcc 4.7 is actually generating buggy code (it would not be the first time,

Well, yeah. GCC 4.7 is still quite new. There is a reason the GCC bugzilla has a class of bugs named 'wrong-code'...

If only I'd not fat-fingered and blown away my git repos I could help looking into that backtrace, but I did and I haven't restored from backup yet.