Re: [trinity-devel] kwrite crash - it's gcc 4.7 - rebuilt 3/29 sources on gcc 4.7 - same crash

On 05/02/2012 09:00 PM, David C. Rankin wrote: I guess the questions now becomes, given all of the backtraces and strace information we have been able to collect, where does it point us to begin? IIRC, Tim's bet is on tdelibs. What about Qt3? tdelibs more probable? Why? As for looking at the code and looking for code that may violate a gcc coding standard - what would you look for? Out of all the backtraces I've looked at, the common entry seems to be: Which, given the symptoms (editor OK until you paste or cursor down to a line that wraps), seems to point to tdelibs/kate/part/katerenderer.cpp:806 if (unicode[z].isSpace()) Is there something violative of some gcc standard in the way .isSpace is called? What about the TOChar::isSpace call at tools/qstring.cpp:475? return ::isSpace( *this ); Same question - anything apparently wrong with this? There were a log of gcc47 FTBFS surrounding needing to add 'this->' to distinguish who's function, etcc.. what being used in the multiple declaration and no forward declaration error. Could one of those exist that gcc doesn't flag, but confuses the execution of the code of whose this is the right 'this' for the program to perform without crashing. Many times looking at the code, especially where templates were used, gcc47 requires the explicit this-> where there are several templates used side by side. Those areas look like a likely place for gcc to get confused with which template is the 'this' template the compiler wants. That's just ramblings at this point. We will actually need somebody to browse the files that have veen flagged in the backraces to look at those areas and see if anything stands out as being noncompliant. I could look all day at the same file and not be able to tell compliant/noncompliant from a hole in the ground. So I won't volunteer and give anyone any unjustified hope of me actually picking something out. What is the best approach here?