ID: 38525
User updated by: judas dot iscariote at gmail dot com
Reported By: judas dot iscariote at gmail dot com
Status: Open
Bug Type: Reproducible crash
Operating System: linux
PHP Version: 5.2.0RC2
New Comment:
BTW... I just tested again with a fresh cvs checkout and :
Squirrelmail 1.4 == segfaulted just after loggin, with the same
backtrace.
Squirrelmail 1.5devel == no segfault, probably 'cause that release
doesn't contains the code that triggers this crash.
in response james at digisys dot net :
regardless what the squirrelmail pages says, it has worked pretty fine
for us in PHP 5.1.x , and anyway, no userspace code should crash the
engine, or at least, not randomly :-)
Previous Comments:
------------------------------------------------------------------------
[2006-08-29 05:39:29] judas dot iscariote at gmail dot com
tony, Im using 1.4.x Tree from CVS.
I hope somebody else can reproduce it, due to the random nature of the
problem, is hard to get a short reproduce code... :-(
------------------------------------------------------------------------
[2006-08-28 06:55:47] [EMAIL PROTECTED]
Christian, what version of SquirrelMail did you use?
------------------------------------------------------------------------
[2006-08-28 01:19:15] james at digisys dot net
FWIW, I'm seeing these same random seg faults with PHP 5.1.4 and
Squirrelmail 1.4.8 with an external IMAP server. Switching to the
development branch of Squirrelmail (1.5.2) cleared things up.
According to the Squirrelmail site the current stable releases (1.4.x)
do not work with PHP5, but the CVS version contains fixes which get it
working. Not that PHP should fault either way :)
------------------------------------------------------------------------
[2006-08-26 09:35:25] poeml at suse dot de
Hi,
on my machine it happens with IMAP server _on localhost_.
A how-to-reproduce procedure here is:
- open inbox in browser
- open first mail
- click "next mail"
- proceed with clicking "next mail" (thereby stepping
through mailbox mail by mail), until segfault happens.
Sometimes it takes a while, but il WILL happen sooner or
later.
- now, reloading will trigger the segfault again and again.
- viewing the next mail and going back shows the mail
without segfault. This also allows to continue to use
squirrelmail until the next segfault is encountered.
------------------------------------------------------------------------
[2006-08-23 23:06:11] [EMAIL PROTECTED]
Well, we still need a reproduce case..
------------------------------------------------------------------------
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/38525
--
Edit this bug report at http://bugs.php.net/?id=38525&edit=1
