Odd code path

[SteveTaylor]

Hello all,

Could someone please confirm that I am not going mad here. The file concerned is up to date and matches the binary that is running:

try
{
    if(!p || !ValidValue(pHelper, pObject))
    {
         return true;
    }
} // HERE
catch(...)
{
    AfxMessageBox("report");             
    return true;   // THERE
}

When I am debugging and I get the line above (HERE) I single step and land on THERE.

I was expected it to miss the catch's brackets out completely, or at least hit the message box. Why would it jump to THERE?

[Eri523]

Is this an optimized build? Both the return true; statements end the function and return the same value, hence the compiler easily can contract them into a few common machine instructions during optimization.

[SteveTaylor]

Thanks for the tip.

I just checked and the build parameters for optimisation is: Disabled (/Od)

[Eri523]

Can you post the disassembly of that code fragment (or perhaps the entire function if it's not too large)?

[SteveTaylor]

How do I do that?

Also, I have tried adding extra lines in etc and the same thing always happens.

The code ALWAYS jumps to the return true. The code then does not actually return from the function but carries on to the next lines.

[Paul McKenzie]

How do I do that?

Also, I have tried adding extra lines in etc and the same thing always happens.

The code ALWAYS jumps to the return true. The code then does not actually return from the function but carries on to the next lines.

You are either

1) Debugging source code that does not match the executable you're running. In other words, the source code the debugger sees is newer or older than the executable that's running.

Check that you're running the executable you think you're running. The usual cause of this is that you may have multiple versions of that executable, and you're starting up another version of the EXE instead of the one you just built.

OR

2) Running an optimized build.

If you need convincing, put an output statement in one of the functions you know will be called. If it's a console program and you use cout, you will see the message. If you don't see the message, then item 1) is the issue.

Regards,

Paul McKenzie

[Eri523]

How do I do that?

While debugging, you can simply select part of the disassembly with the keyboard or mouse and copy it to the clipboard like any other text. If you don't have the disassembly window open, you get it by pressing Alt+8 (not Alt+F8) or via the menu under Debug -> Windows.