[BUG] Segmentation fault with callProcedure

[midbel]

Describe your system

• odbc Package Version: 2.4.8
• ODBC Driver: unixODBC
• Database Name: DB2 on ibmi 7.4
• Database Version:
• Database OS:
• Node.js Version: 22
• Node.js OS: linux ubuntu

Describe the bug
calling function callProcedure on an open connection ends with a Segmentation fault. We've also tried with a prepared statement and the call to the same procedure works. Our procedure take only a varchar as a INOUT parameter. We've try with a char(500) as an IN parameter and a second OUT parameter, but the segmentation fault still appears. The input parameter is JSON string and we're expecting to retrieve a JSON object as string from the INOUT parameter.

the connection used is obtained from a pool

Expected behavior
no segmentation fault occurs when using the callProcedure function

To Reproduce
Steps to reproduce the behavior:

1. Connect to database with options '...'
2. Create database table '...'
3. Run query '...'

Code
we used the following code to reproduce the issue

import odbc from 'odbc';


(async () => {
    const dsn = "<connection string>"
    let conn;
    try {
        conn = await odbc.connect(dsn);
        console.log("conn", conn.odbcConnection)
        console.log("connected", conn.connected)
        const data = {action: 'CR', data:{numcli: 103, price: 10}};
        console.log("data", data);

        const res = await conn.callProcedure(null, 'SCHEMA', 'TEST_PROC', [JSON.stringify(data)])
        console.log(res2)
    } catch (err) {
        console.error('oups something wrong happens!');
        console.error(err);
    } finally {
        if (conn) {
            await conn.close()
        }
    }
})();

Additional context
the application runs into a docker container with node-22-slim as base image