The DBM-Functions on Windows truncates the values (cuts 1. char)

examplecode:

<?php
$d = dbmopen('testfile.dbm', 'c');
 dbminsert($d, '0', 'Testtext1');
 dbminsert($d, '1', 'Testtext2');
 dbminsert($d, '2', 'Testtext3');
 echo  dbmfetch($d, '0') . '<br>';
 echo  dbmfetch($d, '1') . '<br>';
 echo  dbmfetch($d, '2') . '<br>';
 dbmclose($d);
?>

Also a problem on Windows 98 and PHP 4.2.0

See my bugreport 18746 for a shorter example.

Dup of 18746... yes I know this came first, but the other one has a shorter example, and a few more comments.

This bug has been fixed in CVS.

 In case this was a PHP problem, snapshots of the sources are packaged
 every three hours; this change will be in the next snapshot. You can grab
 the snapshot at http://snaps.php.net/.
 
 In case this was a documentation problem, the fix will show up soon at
 http://www.php.net/manual/.

 In case this was a PHP.net website problem, the change will show
 up on the PHP.net site and on the mirror sites in short time.
 
Thank you for the report, and for helping us make PHP better.

okay, we *thought* we'd fixed it ...  sorry ...

[marcus@zaphod php4-HEAD]$ php -r 'ini_set("magic_quotes_runtime",1);$db=dbmopen("db","n");dbmreplace($db,"7","alpha");var_dump(dbmfetch($db,"7"));dbmclose($db);'
string(5) "alpha"

My windowsXP reports:
string(6) "lpha\0"

that means the original length of the windows result is 5
"lpha" plus one zero byte.

that implies the fetch function starts reading after 'a' or
skips 'a' on windows. 

the only thing i can think of is fgets() returns the wrong 
filepointer on windows or read() starts reading at current 
offset +1. Maybe this is because we are mixing fgets with read perhaps we should use fgets twice.

This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at http://snaps.php.net/.
 
In case this was a documentation problem, the fix will show up soon at
http://www.php.net/manual/.

In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites in short time.
 
Thank you for the report, and for helping us make PHP better.

My suggestion turned out to be the solution to this.