'invalid request BLR' puts actual error (and procedure where it happened) at the end where it is truncated by ISC API

[ppazera]

When preparing to switch application written in Delphi using IBObjects from 2.5 to 5.0 we noticed new 'Missing arg #1 - possibly status vector overflow' errors in multiple places, for example:

SQL: select * from ex_ssccPkg_getList (561161, -1, -1, null, f_now(), 5004, '12/31/2020', 1, 0, 1)
ISC ERROR CODE:335544876
ISC ERROR MESSAGE:
Error while parsing procedure EX_SSCCPKG_GETLIST's BLR
Error while parsing procedure INT_SSCCPKG_GETLIST4's BLR
Error while parsing procedure INT_FCCPLANIDS_VALIDATE's BLR
Error while parsing procedure INT_BROADBANDLABELS's BLR
Error while parsing procedure <Missing arg #1 - possibly status vector overflow>'s BLR

note that procedure list unusually starts with parent, thus I quite likely the error is at the end of the list and was truncated by ISC API

without seeing actual error and where it happened we did not have clues how to reproduce and show the problem

later we bumped into another scenario which is reproducible -- create a few stored procedures, from youngest child call existing UDF function, then rename UDF and call parent procedure

in 2.5 there was error first and then silently truncated procedure list:

invalid request BLR at offset 979
-function F_NOW is not defined
-module name or entrypoint could not be found
-Error while parsing procedure INT_GET_USER's BLR
-Error while parsing procedure INT_USERS_GETCURRENTPK's BLR

in 5.0 procedure list is reversed and error is at the end (visible in isql via OO API):

Error while parsing procedure INT_CONNECT_CONTEXTS's BLR
-Error while parsing procedure INT_USERS_GETCURRENTPK's BLR
-Error while parsing procedure INT_GET_USER's BLR
-invalid request BLR at offset 976
-function F_NOW is not defined
-module name or entrypoint could not be found

but when using IBO which uses ISC API only first 4 lines are shown, followed by 'Missing arg #1 - possibly status vector overflow':

Error while parsing procedure INT_CONNECT_CONTEXTS's BLR
Error while parsing procedure INT_USERS_GETCURRENTPK's BLR
Error while parsing procedure INT_GET_USER's BLR
invalid request BLR at offset 976
function <Missing arg #1 - possibly status vector overflow> is not defined

actual error that UDF function entry point was not found is missing. If there were couple more procedures involved, then we would not see in which procedure error happened

I hope that original errors we bumped into are also 'invalid request BLR' and putting error at the top and reverting procedure list like it used to be in 2.5 would allow us to see what's happening there

Thanks,
Paulius