[Qt-creator] QtCreator Crash under RHEL5 (Code Syntax Related?)

[Victor Sardina]

Fellows:

I just confirmed that this crash doesn't happen under Mac...only under
Linux.

Victor

On 4/24/10 6:23 PM, Victor Sardina wrote:
> Fellows:
>  
> I don't know if this would help fix the problem, but find below some 
> more information on the crash. For more detailed information I would 
> have to recompiled QtCreator in debug mode, but the output below hints 
> (I hope) to the source/location of the crash, namely:
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x00002aaaace72432 in CPlusPlus::BackwardsScanner::mid ()
>    from 
> /usr/local/Trolltech/Qt-4.7.0/qtcreator/lib/qtcreator/plugins/Nokia/../.               
> ./libCPlusPlus.so.1
> 
> Victor
> 
> ===============================================================
> GNU gdb Fedora (6.8-37.el5)
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-redhat-linux-gnu"...
> (no debugging symbols found)
> (gdb) run
> Starting program: /usr/local/Trolltech/Qt-4.7.0/qtcreator/bin/qtcreator.bin
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> [New Thread 0x2b90c93f4390 (LWP 7117)]
> [New Thread 0x41df5940 (LWP 7123)]
> [Thread 0x41df5940 (LWP 7123) exited]
> [New Thread 0x41df5940 (LWP 7128)]
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> QColor::setNamedColor: Unknown color name ''
> [New Thread 0x427fa940 (LWP 7129)]
> Detaching after fork from child process 7130.
> [New Thread 0x431fb940 (LWP 7135)]
> [New Thread 0x43bfc940 (LWP 7136)]
> Detaching after fork from child process 7137.
> Detaching after fork from child process 7138.
> Detaching after fork from child process 7139.
> Detaching after fork from child process 7140.
> Detaching after fork from child process 7141.
> Detaching after fork from child process 7142.
> Detaching after fork from child process 7143.
> Detaching after fork from child process 7144.
> [New Thread 0x445fd940 (LWP 7145)]
> [New Thread 0x44ffe940 (LWP 7146)]
> [New Thread 0x459ff940 (LWP 7147)]
> [Thread 0x445fd940 (LWP 7145) exited]
> [New Thread 0x445fd940 (LWP 7148)]
> [New Thread 0x46400940 (LWP 7149)]
> [Thread 0x44ffe940 (LWP 7146) exited]
> [Thread 0x459ff940 (LWP 7147) exited]
> [New Thread 0x459ff940 (LWP 7150)]
> Detaching after fork from child process 7153.
> Detaching after fork from child process 7155.
> [New Thread 0x44ffe940 (LWP 7157)]
> [New Thread 0x46e01940 (LWP 7158)]
> [Thread 0x46400940 (LWP 7149) exited]
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x00002aaaace72432 in CPlusPlus::BackwardsScanner::mid ()
>    from 
> /usr/local/Trolltech/Qt-4.7.0/qtcreator/lib/qtcreator/plugins/Nokia/../.               
> ./libCPlusPlus.so.1
> 
> 
> Victor Sardina wrote:
>> Fellows:
>>
>> I happened to come across a rather unusual crash of QtCreator under 
>> RHEL5. I will try to explain the steps to reproduce the crash:
>>
>> 1) Go to a function implementation line, like:
>>  
>> int FooClass::FooFunction(int const& i, int const& j,
>>                                            int const& k, int const& h)
>> {  ...
>>     ...
>> }
>>
>> and  break it down like so:
>>
>>  int FooClass::FooFunction
>>    (int const& i, int const& j,
>>     int const& k, int const& h)
>> {  ...
>>     ...
>> }
>>
>> 2) Then go to the end of the first line of arguments, erased the "," and 
>> try writing it back...
>>
>> I get an instant crash each time I try to do this under RedHat 5. At 
>> first I thought that it had something to do with the FakeVim plugin, but 
>> no, it happens even when not using the FakeVim plugin. This appear to 
>> indicate that for some reason the Editor can't cope with the parsing of 
>> code written in that manner, maybe something to do with the handling of 
>> the scope operator "::"? Whatever the reason, this happens each time you 
>> follow 1) and 2) above. I will try it under Mac tomorrow and see what 
>> happens.
>>
>> Has anyone seen this behaviour before?
>>
>> Victor
>> _______________________________________________
>> Qt-creator mailing list
>> Qt-creator at trolltech.com
>> http://lists.trolltech.com/mailman/listinfo/qt-creator
>>   
> 
> _______________________________________________
> Qt-creator mailing list
> Qt-creator at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator

-------------- next part --------------
A non-text attachment was scrubbed...
Name: victor_sardina.vcf
Type: text/x-vcard
Size: 577 bytes
Desc: not available
Url : http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20100425/b7a63b17/attachment.vcf