Bug #17580 Updated: PARSE_INI_FILE exits on files larger than 16KB
| From: | alex at acid-edge dot net | Date: | Mon, 10 Jun 2002 19:08:59 +0000 |
| Subject: | Bug #17580 Updated: PARSE_INI_FILE exits on files larger than 16KB | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-10032@lists.php.net to get a copy of this message | ||
ID: 17580
Updated by: alex@acid-edge.net
Reported By: jorg.zimmermann@ron.de
Status: Open
Bug Type: Reproducible crash
Operating System: windows NT 4.0/XP/2000
PHP Version: 4.2.1
New Comment:
Trying to parse Winamp .pls files and had to rely on a dodgy class
someone wrote - however I don't get any error, PHP just seems to exit
with no warning :/
Previous Comments:
------------------------------------------------------------------------
[2002-06-03 18:41:08] jorg.zimmermann@ron.de
not a zillion, :) you can hit this limit with barely 300 keys and 55
char per line ...
------------------------------------------------------------------------
[2002-06-03 18:31:23] mfischer@php.net
confirmed, just create a testfile with zillions of key=data entries,
you will hit the limit somewhen.
Seems to be dependant on the flex code for ini scanner in Zend. Is it
really worth the trouble ... ?
------------------------------------------------------------------------
[2002-06-03 18:26:30] jorg.zimmermann@ron.de
sorry this is not the case,
it is standard windows ini file format.
[xxx]
key1=data
key2=data
.
.
.
and i do get a regular array on files <16k
there is a \r\n at the end of each line
------------------------------------------------------------------------
[2002-06-03 18:19:57] jorg.zimmermann@ron.de
this is not the case,
it is standard windows ini file format.
[xxx]
key1=data
key2=data
.
.
.
------------------------------------------------------------------------
[2002-06-03 13:13:49] sander@php.net
AFAIK this error only appears if you have more than x kB (apparently
16) on one line. Because that's not a strict limitation at all, I'm
closing this one.
If you think this is not correct, please reopen this report.
------------------------------------------------------------------------
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
http://bugs.php.net/17580
--
Edit this bug report at http://bugs.php.net/?id=17580&edit=1