Bug #79277 [Com]: pdo_odbc accessing SAP 16.0 ASE Fatal error: Allowed memory size ...

Edit report at https://bugs.php.net/bug.php?id=79277&edit=1 ID: 79277 Comment by: dbccjob at gmail dot com Reported by: khleung at isfactory dot com Summary: pdo_odbc accessing SAP 16.0 ASE Fatal error: Allowed memory size ... Status: Open Type: Bug Package: PDO ODBC Operating System: CentOS 7 PHP Version: 7.4.2 Block user comment: N Private report: N New Comment: Is your SAP odbc library symlinked to the SQLLEN8 library version ? The issue you are facing makes think of it. make sure the library points to the sqllen8 one, unless you run on an old linux. libsybdrvodb.so -> libsybdrvodb-sqllen8.so see http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc20155.1600/doc/html/san1361915533650.html Previous Comments: ------------------------------------------------------------------------ [2020-09-29 14:12:56] cmb@php.net > It appears that the issue can be reproduced 100% of the time if > a nullable varchar column getting selected actually contains a > null value. I cannot reproduce this with either the ODBC Driver for SQL Server or the MySQL ODBC 8.0 Unicode driver on Windows, so this is apparently driver (manager) specific. Anyhow, after having another look at this issue, I still have no idea where this excessive memory allocation would occur. I think that addressing the unitialized displaysize issue, and also the -Wpointer-sign warnings is appropriate, but unless that resolves this issue, targeting the "master" branch seems to be more reasonable. ------------------------------------------------------------------------ [2020-08-10 17:40:02] khleung at isfactory dot com net_surfer is right! Please advise any quick fix for that. ------------------------------------------------------------------------ [2020-07-01 19:52:29] net_surfer at mail dot com It appears that the issue can be reproduced 100% of the time if a nullable varchar column getting selected actually contains a null value. ------------------------------------------------------------------------ [2020-03-22 12:31:23] cmb@php.net Indeed, apparently there are no negative display sizes. I'm at a loss; that probably needs to be debugged with a Sybase DB. ------------------------------------------------------------------------ [2020-03-22 12:25:24] khleung at isfactory dot com [sybase@localhost ~]$ php sybconnect.php dsn: odbc:SB007H Connected to ASE 16 displaysize == 255 displaysize == 11 displaysize == 11 displaysize == 2 displaysize == 6 displaysize == 6 displaysize == 6 displaysize == 6 displaysize == 11 displaysize == 23 displaysize == 23 displaysize == 11 displaysize == 11 displaysize == 11 displaysize == 11 displaysize == 11 displaysize == 6 displaysize == 11 displaysize == 6 displaysize == 24 displaysize == 30 displaysize == 39 displaysize == 6 displaysize == 16 displaysize == 6 displaysize == 3 displaysize == 3 displaysize == 11 displaysize == 11 Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 4294967320 bytes) in /home/sybase/sybconnect.php on line 14 [sybase@localhost ~]$ Seems not what you guess ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=79277 -- Edit this bug report at https://bugs.php.net/bug.php?id=79277&edit=1