Bug #12379 PROCEDURE with HANDLER calling FUNCTION with error get strange result

Description:
A procedure with a handler for SQLEXCEPTION that calls a STORED FUNCTION (not a UDF) that returns an error, will return strange data or get into a loop in some cases. Might be related to 7049, I don't know, they seem to deal with similar issues.

How to repeat:
Create these objects:
DROP TABLE IF EXISTS t1;
CREATE TABLE t1(c1 CHAR(1));

DROP FUNCTION IF EXISTS myfunc;
delimiter //
CREATE FUNCTION myfunc()
RETURNS INTEGER
BEGIN
   DECLARE v1 INTEGER;

   INSERT INTO t1 VALUES('X', 'Y');
   RETURN 0;
END;
//
delimiter ;

DROP PROCEDURE IF EXISTS myproc1;
delimiter //
CREATE PROCEDURE myproc1()
BEGIN
   DECLARE EXIT HANDLER FOR SQLEXCEPTION SELECT 1;

   SELECT myfunc();
END;
//
delimiter ;

DROP PROCEDURE IF EXISTS myproc2;
delimiter //
CREATE PROCEDURE myproc2()
BEGIN
   DECLARE EXIT HANDLER FOR SQLEXCEPTION BEGIN END;

   SELECT myfunc();
END;
//
delimiter ;

Now, to see the errors:
mysql> call myproc1();
ERROR 2027 (HY000): Malformed packet
mysql> call myproc2();
-- The above will loop and loop and loop....

Or rather, the call to myproc2() will hang, I guess... Anyway it doesn't return.

Below the current behavior with BK source server:

mysql> call myproc1();
ERROR 2027 (HY000): Malformed packet
mysql> call myproc2();
Packets out of order (Found: 5, expected 1)
ERROR 2013 (HY000): Lost connection to MySQL server during query
mysql>

Changed priority since the dropping a connection is more than non-critical

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/29375

Proposed a more general solutuion in review email. Need more discussion to decide which solution is better

Noted in 5.0.13 changelog.