INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10

It would appear that LVARCHAR return types can under some 
circumstances over write memory causing all sort of different 
failures. 
 
The SPL code involved has both nested and recursive SPL calls, 
each returning a LVARCHAR and as the return value for the 
LVARCHAR seemed to increase in subsequent calls, the memory for 
the LVARCHAR seemed to be not large enough and eventually wrote 
outside it's bounds and caused memory corruption. 
 
One particular AF looked like this: 
 
08:58:34  Found during mt_shm_free 1 
08:58:34  Pool '82397' (0x113116040) 
08:58:34  Bad block header 0x125958400 
blk-64 
00000001259583c0: 6e64206d 6f6e6579 20696e20 61207265   nd money 
in a re 
00000001259583d0: 73746175 72616e74 20776974 68206261   staurant 
with ba 
00000001259583e0: 64206375 73746f6d 65722073 65727669   d custom 
er servi 
00000001259583f0: 63652e20 43757374 6f6d6572 2063616d   ce. Cust 
omer cam 
blk+64 
0000000125958400: 6520696e 20746f64 61792062 65636175   e in tod 
ay becau 
0000000125958410: 73652068 69732064 61756768 74657220   se his d 
aughter 
0000000125958420: 77616e74 65642074 6f206561 74207768   wanted t 
o eat wh 
0000000125958430: 69746520 63617374 6c652e00 00000000   ite cast 
le...... 
 
There should have been a block header at 0x125958400, but you 
can clearly see a string appears to have exceeded it's bounds 
and continued on into the following block header corrupting it. 
This string should have been allocated for a return value of 
LVARCHAR type from a SPL call.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Recursive Stored procedures                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 12.10xC5 or earlier PID if available              * 
****************************************************************

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

16.07.2014
16.10.2015
16.10.2015

12.10.xC5