On 05/04/2012 07:36 PM, Timothy Pearson wrote:
Darn. I was running out the door when I wrote that; I'll try to get something better to you later.
All of these crashes appear to be the result of a TQString passed by reference from katerenderer.cpp that is disappearing before it is fully processed.
just a guess: could it be that that TQString is created and destroyed in a different thread than that which uses it (and consequently crashes)?
nik
It is possible, that is why I am allowing gcc to handle any passing by reference with the patch I posted. It is possible that gcc was inlining the functions (and masking the potential crash) prior to gcc 4.7.
This is all just a shot in the dark until I can reproduce the bug here. ;-)
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Ooh! Tim, kwrite really, really hates your patch! It opened OK, but the first character I tried to type cause it to explode:
OK, this will have to wait until I can get a gcc 4.7 system up and running.
Tim