Creator debugger nearly unusable due to debug optimizations

Tested using "uic" project from qtbase. Issues:

1. Cannot set the breakpoint in a pointed line.

To reproduce:

Set some breakpoints in cppwriteinitialization.cpp file:
A) line 1137: const bool isTopLevel = m_widgetChain.count() == 1;
B) line 1393: propertyValue = autoTrCall(p->elementString());

After running the debugger, breakpoints are moved:
A to 1140 line: DomPropertyMap properties = propertyMap(lst);
B to 1394 line: break;

"A" jumps inside the if condition, so after running the debugger it doesn't stop there at all.

2. When stepping over manually sometimes debugger steps into some method invocation.

3. The call stack sometimes looks wrong and works wrong. It shows the right function name, but points to the wrong file. Double click jumps to the wrong file, too.

4. In some cases I can't step into the function, it steps over.

It looks like when I remove the -Og option from mkspecs/common/gcc-base.conf, all the above issues are gone. This was introduced in: https://codereview.qt-project.org/#/c/177019/

Screenshots:
debugger1 - all methods are in the same file, but debugger shows the wrong file for 2nd and 3rd file.
debugger2 - after double click on the selected method inside call stack, it jumps to the wrong file in editor
debugger3 - after running the debugger, the breakpoint is moved from 1393 to 1394 line, what doesn't make sense.