Last affectation (right before the END) can't be visualized in debugger

[Kurairaito]

With the folowing procedure :

DELIMITER //
CREATE PROCEDURE `test_procedure2`() NOT DETERMINISTIC NO SQL SQL SECURITY DEFINER BEGIN
	DECLARE test_TINYINT TINYINT;
	SET test_TINYINT = 1;
	SET test_TINYINT = 2;
	SET test_TINYINT = 3;
END//
DELIMITER ;

when executing :

DELIMITER //
$install
$setup test_procedure2
$debug test_procedure2();
$NEXT
$refresh variables
SELECT * FROM xxxmdbug.variables;
$NEXT
$refresh variables
SELECT * FROM xxxmdbug.variables;
$NEXT
$refresh variables
SELECT * FROM xxxmdbug.variables;
$NEXT
$refresh variables
SELECT * FROM xxxmdbug.variables;

you will have the folowing output value :

test_TINYINT = null
test_TINYINT = 1
test_TINYINT = 2 (old_value =1)
test_TINYINT = 2 (old_value =1)

instead of

test_TINYINT = null
test_TINYINT = 1
test_TINYINT = 2 (old_value =1)
test_TINYINT = 3 (old_value =2)

Edited to replace boolean by tinyint as value 2 and 3 could be confusing for a boolean value.... (even if boolean doesn't exist in SQL)

[pgulutzan]

Actually it's not a bug.
If you look at the Debugger status line you will see
"
result: debuggee_wait_loop ended)(STOPPED AT ROUTINE EXIT)
"
If you look at the result of $refresh variables you will see the message
"
mysql>$refresh variables;
Routine has stopped. Suggested next step is: $EXIT
"

One way to look at it is:
$refresh can only work if you're at a breakpoint.
Breakpoints can only happen for executable statements.
But there are no executable statements because the procedure ended.

One way to work around it is:
Put an executable statement at the end and put a breakpoint on it.

I will keep this open as a feature request by
setting the "enhancement" label.
It might be possible to add an option for
"breakpoint on routine exit" or
"always refresh variables on routine exit".
If multiple people request this, it will be expedited.