Is it possible to modify debug process to let the execution linger in the
debugged function for 1 more step to show the result created by the return
statemenet in the debug view?
This way there will be no need to create temp variables/debug statements to
debug what the actual return statement of
Here is an example screenshot:
http://s3.postimg.org/rxzh6trub/16_11_2015_14_02_06.png
The result of the return can neither be seen in the locals section, nor
added as an expression.
On Mon, Nov 16, 2015 at 1:55 PM, NIkolai Marchenko
wrote:
> locals and expressions
locals and expressions only show just that: locals and expressions
When there is a chain of returns none of which assign to a temporary
variable it become hard to debug what went wrong and where without modifyng
code with qdebugs
On Mon, Nov 16, 2015 at 1:47 PM, Orgad Shaneh
Hi,
Am 16.11.2015 um 11:47 schrieb Orgad Shaneh:
When you exit a function with Shift-F11 the return value is displayed
in the Locals view.
This is a feature of the gdb engine inside creator. The cdb engine
doesn't have that feature. I'm not quite sure about the lldb engine.
Greetings