Limited number of "if-statements"

[patrickfrei]

Hello

I noticed that there seems to be a limited number of 12 "if-statements" in a "for-statement". If a add more than 12 "if-statements" the application crashes. My programming structur is as follows:

for (condition)
{
     if (condition)
     { }
     if (condition)
     { }
     if (condition)
     { }
     ...
}

Is that true or could it that there is a potential programming error in that structure??

[wizard_hu_]

Guess, which is the more probable:
- a programming language used worldwide by millions of software developers limits the occurences of a specific statement inside a loop
- you have made an error

[kiran10182]

Hi Patrickfrei,

Hello

I noticed that there seems to be a limited number of 12 "if-statements" in a "for-statement". If a add more than 12 "if-statements" the application crashes.

It should not be a problem.
There might be something wrong with your code.

Regards.
Kirann

[hotcheese]

Guess, which is the more probable:
- a programming language used worldwide by millions of software developers limits the occurences of a specific statement inside a loop
- you have made an error

Actually, historically there have been quite a lot of defects in the compilers that Symbian has used that have been exposed by code such as this. These were mainly with the gcc compilers.
They've probably all been discovered and rectified by now, most of them were discovered years ago, but compilers are code too and also therefore can contain defects.

[dhaas]

I've personally run into problems with gcc in the S60 3rd SDK mis-optimizing. The project worked perfectly before, but after a recompile with "-O2 -fno-unit-at-a-time", the code started crashing the phone when entering a certain very innocuous function. When I put logging statements in to see what was going on, it didn't crash any more...so eventually, it was tracked down that the crash was happening between the line that was "float x;" and "if(bWhatever == true) ...". I'm sure everything in the if statement is perfectly valid C++(not even any particularly exotic code), so that wasn't an issue. What was the solution? Put in between those two lines "int _notused;"

So the only solution ended up adding a variable never used warning :'(

[symbianyucca]

anyway, with Symbian you shoduln't use this : "if(bWhatever == true)", instead you should use as "if(bWhatever)" only. And I'm quite sure that it is recommended to use EFalse & ETrue definitions with TBool variables, where EFalse is zero and ETrue can be any positive value.

yucca

[patrickfrei]

Hmm, I looked through the code again and everything seems to be o.k.!! But after 12 if-statements the application crashes immediately...

In the if-statements I have code like this:

if (aDescription[ s ].Compare(_L("Manufacturer")) == 0)

Does someone have an idea for modifying the above code??

[david.caabeiro]

Why don't you post the exact snippet? Otherwise it's difficult to tell..

[patrickfrei]

I can't post it because the code is of about 300 lines...

...but what I meant is if it makes sense to change the code from:

if (aDescription[ s ].Compare(_L("Manufacturer")) == 0)

into

if (!aDescription[ s ].Compare(_L("Manufacturer")))

...because ==0 is FALSE --> that should not be use according to the posts above --> !

What do you think?

[alcoran]

What kind of crash is it? a Panic? which one? does it occurs on device only or with emulator?
If it's on device only consider that it could be a stack overflow error, which symptom is a kern-exec-3. from what you describe (300 lines function, _L used instead of _LIT..) this is a possibility.

[patrickfrei]

The crash obviously occurs on phone only. I can't tell that with 100% reliability because the information the code displays depends on the HAL information (on the phone there are a lot more information than on the emulator --> i.e. not every if-statement is used on the emulator).

No message is being displayed on crash. The application simply "disappears"...

Would you use _LIT instead of _L (even if you use a string only once)??

[david.caabeiro]

You are probably running out of stack memory.. Do this:

_LIT(KManufacturer, "Manufacturer");

if (aDescription[ s ].Compare(KManufacturer) == 0)
...

[vin2ktalks]

...

No message is being displayed on crash. The application simply "disappears"...

...

As PushL has mentioned use _LIT, but one more thing why can't you create an ErrRd and check the exact reason for the application crash?