RFQ/BOM 0 Sign In / Register

Select Your Location

user image

The if statement encountered during C language debugging is invalid, but it can be executed.

MCU
November 25, 2020 by Deja 1679

The phenomenon encountered when debugging the board.

The if statement does not hold true. The value of ret is 0, but the if (1==ret) statement can be executed. what's going on. Has anyone come across it? Please advise.

All Comments

user image

Krista Posted on November 25, 2020

I often encounter this situation. I don't know why, but the strange thing is that it doesn't affect my judgment in the end.

0
user image

Leona Posted on November 25, 2020

It should be the reason for compiler optimization. Just look at the assembly code. It is estimated that the code is still there in other places.

0
user image

Reggie Posted on November 25, 2020

1. Reduce the optimization level;

2. ret is defined as uint32_t;

0
user image

Dorothy Posted on November 25, 2020

I have encountered this. It should be a problem with the debugger. Sometimes the variable value displayed by the debugger is not updated in time. Because your ret is initialized to 0, you can try to initialize the ret to a different value when it is defined. Whether the initial value is displayed here.

0

Write an answer

You need to log in to reply. Sign In | Register