causes the problem I mentioned yesterday... I
remembered that I'm actually URL encoding the data prior to encrypting it so the
string is really "Reed%2C+Phyllis". The key is still
"70094cc48e1a23bf6fec60c2db6e4b71"...
Take care
l as
with every available release of libmcrypt (2.4.7-2.4.15) all without effect. Given
that I have the same problem on a production webserver at phpwebhosting as I do on my
own homemade PPC linux box I'm guessing this is real problem...
Any thoughts would be greatly apprecia
he problem.
kpw
---
[2001-05-27 19:27:02] [EMAIL PROTECTED]
Should be fixed in CVS now. Fix will be in PHP 4.0.6.
If this happens with it too, reopen this bug report.
ID: 10324
User Update by: [EMAIL PROTECTED]
Status: Open
Bug Type: Reproduceable crash
Description: reproducable seg fault during generic script exec with pgsql and mcrypt
here's the back trace (again without db symbols) of the crash when it happens after my
script has completed execution:
Pr
ID: 10324
User Update by: [EMAIL PROTECTED]
Old-Status: Feedback
Status: Open
Bug Type: Reproduceable crash
Description: reproducable seg fault during generic script exec with pgsql and mcrypt
I've rebuilt php with --enable-debug on (rm config.cache & cleaned the build dirs),
but the db symbols
From: [EMAIL PROTECTED]
Operating system: Linux PPC (yellow dog 1.2)
PHP version: 4.0.4pl1
PHP Bug Type: Reproduceable crash
Bug description: reproducable seg fault during generic script exec with pgsql and
mcrypt
Hi,
I've managed to uncover a reproducable segmentation fau
