Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Linux: Crashes
moloh:
--- Quote from: thomas on May 15, 2006, 11:32:29 pm ---Not strange at all.
I understand that you have a certain frustration if things don't work for you, but this statement is outright nonsense, and you know it.
The TinyXML problem is not what crashes you, it just provokes a warning from valgrind. You said that yourself the other day.
As you have been told, it has been fixed long ago, but has not been merged to the trunk yet. As it is not a real problem (it is not pretty, it is technically not correct, but that's it), there is no urgent reason to get dippy about it now.
--- End quote ---
I can agree with that, in true i'am a little bit flustrated. Things just don't work as easy as they suppose to. But i am also kind of idealist, if there is a warning it should be suppressed somehow and that is why i don't like things like that left behind.
--- Quote from: thomas on May 15, 2006, 11:32:29 pm ---The crash is thread-related. The only thing that uses threads (other than the main thread) is the code completion plugin, so you may want to try turning that off.
--- End quote ---
I will try that.
--- Quote from: thomas on May 15, 2006, 11:32:29 pm ---The next thing ("Conditional jump or move depends on uninitialised value(s)") is very likely about CompileTargetBase::m_OptionsRelation[] which is not initialised in the constructor. It is not pretty but it is not a bug either (and not the reason for a crash). Although the variable appears uninitialised, it is not. It is true that the constructor doesn't initialise it, but that's done in another place.
--- End quote ---
If it is then it is initialized after this call or there is some valgrind bug.
Thanks for interest in these issues.
thomas:
--- Quote ---If it is then it is initialized after this call or there is some valgrind bug.
--- End quote ---
Whatever it is, it has no great consequences.
The absolutely worst thing to happen (if the variable was *really* uninitialised) would be the project file being incorrectly flagged as "modified" on startup. This, however, never happens (we would know if that ever happened!).
So this is really not a problem. :)
moloh:
--- Quote from: thomas on May 16, 2006, 12:29:10 am ---
--- Quote ---If it is then it is initialized after this call or there is some valgrind bug.
--- End quote ---
Whatever it is, it has no great consequences.
The absolutely worst thing to happen (if the variable was *really* uninitialised) would be the project file being incorrectly flagged as "modified" on startup. This, however, never happens (we would know if that ever happened!).
So this is really not a problem. :)
--- End quote ---
Ok, now i belive You. ;-)
Navigation
[0] Message Index
[*] Previous page
Go to full version