ID: 9775
Updated by: derick
Old-Status: Assigned
Status: Suspended
Bug Type: Reproduceable crash
PHP Version: 4.0.4pl1
Assigned To: derick

I can reproduce this on my own system, both thtough PHP and with a C-program. As the 
author of libmcrypt cannot reproduce this, I'll suspend this bug until I know more 
about it.

Previous Comments:

[2001-04-16 07:10:58] [EMAIL PROTECTED]
I committed the fix for the memleak, but the crash is most likely a problem in 
libmcrypt, because I had those some things when running a C program which uses these 
functions. The author of libmcrypt says this can be a problem in different versions of 
libltdl, but I had the same problem with both the 1.2 and 2.0 versions. I'm awaiting 
further response from Nikos now.


[2001-04-16 05:30:50] [EMAIL PROTECTED]
Derick Ill assign this one to you so you remember it.. you said you had a fix.

- James


[2001-03-16 09:36:27] [EMAIL PROTECTED]
These memleaks where indeed caused by not freeing the key. Fix is pending until I have 
access to CVS again.


[2001-03-16 09:26:03] [EMAIL PROTECTED]
Those memleaks can in no way crash php too. It seems to
me that the key is not freed. I'll check this part out.


[2001-03-15 23:09:58] [EMAIL PROTECTED]
I had those same segfaults but after I updated my GDB to
version 5.0 they didn't happen again. So please try
updating your GDB and try generating the backtrace for
the crashes again. FYI: The author of libmcrypt has 
said that some of these crashes are actually bugs in
the libmcrypt itself..



The remainder of the comments for this report are too long.  To view the rest of the 
comments, please view the bug report online.

ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to