Re: Anybody knows this bug ?

Bug B42571 has been coded in the version under development (6.04/4.16). Bug B42675 is a duplicate of bug B42571. All prognostications of release dates need to be taken with suitably large pinches of salt, but this should be available in 96Q3 (July?). The bug is only known to affect p-code programs. The bug was not in the release notes because we didn't know it existed when the product was released. If we had known about it, it would probably not have been released! I would regard it as a show-stopper bug. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> }From: brent@advgroup.co.nz (Brent Jackson) }Date: Sun, 17 Mar 1996 22:37:57 GMT }X-Informix-List-Id: <news.22211> } }kerry@kcbbs.gen.nz (Kerry Sainsbury) wrote: }>In article <4ia08n$31e@yoda.adv>, brent@advgroup.co.nz (Brent Jackson) wrote: }>>laplo@vir.com (Louis Lapointe) wrote: }>> }>>>We are experiencing bad crashes with some of our programs. It happens }>>>when we call another program that returns a value. }>> }>>>For example, }>>> run l_var_run returning l_status }>> }>>>The called program will run normally but the calling program will }>>>crash on the retunring statement. }>> }>>Yep, we've seen it... }>>Informix support told us it was a known bug, and the "workaround" was to }>>remove the RETURNING clauses from RUN statements (great, huh :). The bug }>>number is 42571 or 42675. } }>Wow -- we got that one too. Actually died on a SELECT statement miles }>after the RUN (took us ages to find it). We got the same fix too } }I can relate to that. It took us about 12 person-hours to isolate the }error. Which is why it was so aggravating to be told by Informix that it }was a "known" bug. It wasn't in the release notes !