php5 crashed with SIGSEGV in strcasecmp()

[siucdude]

Binary package hint: php5

This has started to happen with end of day updates on 9/13/2010, cant seem to figure it out but looks bad. directions to debug can help.
Thank YOu
TJ

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: php5-cli 5.3.3-1ubuntu6
ProcVersionSignature: Ubuntu 2.6.35-21.31-generic-pae 2.6.35.4
Uname: Linux 2.6.35-21-generic-pae i686
Architecture: i386
CrashCounter: 1
Date: Sun Sep 12 20:25:01 2010
ExecutablePath: /usr/bin/php5
ProcCmdline: /usr/bin/php -q /usr/share/egroupware/phpgwapi/cron/asyncwrapper.php
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x98ed3a <strcasecmp+74>: movzbl (%esi,%edx,1),%esi
 PC (0x0098ed3a) ok
 source "(%esi,%edx,1)" (0x06b8c386) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: php5
StacktraceTop:
 strcasecmp () from /lib/libc.so.6
 ?? ()
 ?? ()
Title: php5 crashed with SIGSEGV in strcasecmp()
UserGroups:

[Thierry Carrez (ttx)]

Waiting on the retracers to get a more complete stack trace.

[Apport retracing service (apport)]

StacktraceTop:
 *__GI___strcasecmp (s1=0x83abb13 "libxml",
 ?? ()
 zend_hash_sort ()
 zend_startup_modules ()
 php_module_startup ()

[Thierry Carrez (ttx)]

Stacktrace is still missing debug info. Looking at it, it looks like zend_hash_sort (in php5-5.3.3/Zend/zend_hash.c) uses strcasecmp as its compar function, and fails.

Does that happen every time you run something specific ? If yes, could you provide us with a reproducer (some code that reproduces the error while not depending too much on the rest of your PHP code) ?

[siucdude (siucdude)]

well as we see this is a test server I use before it hits the production server. I ran updates this afternoon and noticed later that PHP had few updates.
it seems that i do not get this error right now and can't reproduce this error. I'm currently trying to work with code in PHP for Zend.
But like I said can't get this error anymore but will keep testing until final version of ubuntu 10.10 is out.
Thank You.
tJ

[Thierry Carrez (ttx)]

Thanks for keeping us posted. I'll mark this bug Invalid for now, please set it back to "New" if you can reproduce the issue.