Bug #72729 [Opn->Fbk]: php-cgi.exe/php_mbstring.dll crash Exception 0xc0000005 Fault offset 0x00026831

From: Date: Wed, 10 Aug 2016 14:05:27 +0000
Subject: Bug #72729 [Opn->Fbk]: php-cgi.exe/php_mbstring.dll crash Exception 0xc0000005 Fault offset 0x00026831
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-203164@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=72729&edit=1

 ID:                 72729
 Updated by:         ab@php.net
 Reported by:        caaguado at xcentra dot com
 Summary:            php-cgi.exe/php_mbstring.dll crash Exception
                     0xc0000005 Fault offset 0x00026831
-Status:             Open
+Status:             Feedback
 Type:               Bug
 Package:            mbstring related
 Operating System:   Windows 10 64bit, Windows 7 64bi
 PHP Version:        7.1.0beta1
 Block user comment: N
 Private report:     N

 New Comment:

@caaguado thanks for the further checks. We still miss usable backtrace (fe check #72451) or
reproduce scenario, so then it's impossible to say what the issue is or what is fixed :( I was
lately trying NGINX+FCGI, but still couldn't reproduce any crash with pure PHP core, all
extensions loaded.

Thanks.


Previous Comments:
------------------------------------------------------------------------
[2016-08-05 13:46:09] caaguado at xcentra dot com

Hi again, sorry for the confusion, but now I took some more time to perform my test cases again for
this fault in detail and while it is _indeed_solved_ with Nginx 1.11.x, I have now confirmed that
unfortunately it _continues_failing_ with Apache 2.4.23 (Apache Lounge binaries).

So, part of the fault (the one specifically related to Apache) is still present.

Kindly let me know whether you need anything from me to help with the investigation.

------------------------------------------------------------------------
[2016-08-05 09:42:29] caaguado at xcentra dot com

Hi,

I'm happy to report that this fault has been fixed on PHP 7.1.0beta2.

According to the "news.txt" changelog, the following fixed for mbstring were implemented:

. Fixed bug #72691 (mb_ereg_search raises a warning if a match zero-width).
  (cmb)
. Fixed bug #72693 (mb_ereg_search increments search position when a match
  zero-width). (cmb)
. Fixed bug #72694 (mb_ereg_search_setpos does not accept a string's last
  position). (cmb)
. Fixed bug #72710 (mb_ereg causes buffer overflow on regexp compile error).
  (ju1ius)

It is clear that this fault was related to one or several of them, and maybe even to other bugs
fixed along beta2.

You can close this ticket if you want. Thanks a lot for your support!

------------------------------------------------------------------------
[2016-08-02 18:15:12] caaguado at xcentra dot com

As I’m not able to attach the MS DebugDiag v2.2.backtrace file that I have generated to this
bug report, I've sent it directly to the person assigned via email. I'm mentioning it here
for future traceability.

Please kindly let me know whether the backtrace is actually useful to you, as even though the PDB
files’ location was correctly defined in the tool, it remained saying that it couldn’t
reach the php_mbstring PDB during analysis, so I’m afraid that the backtrace could be not good
enough for troubleshooting.

If that’s the case, I will try something else or will use an older version of the tool.

------------------------------------------------------------------------
[2016-08-02 11:32:30] caaguado at xcentra dot com

Actually, I have now found out why php-cgi.exe crashes twice on Nginx: Once when launching the
process to listen on port 9000, and another time when actually processing the request for the given
PHP script via Nginx.

When it comes to the PHP script itself, it is a very very basic one, including only a call to
function phpinfo(); -and nothing else but this call, so I guess it's not even related to the
actual PHP code executed-

I'm still struggling with MS' Debug Diag tool for it to find the PHP 7.1.0beta1 PDB files
during analysis phase. I'm looking for ways to fix it. I might need to resort to a version
older than v2.2 (¿?).

I will come back to you asap...

------------------------------------------------------------------------
[2016-08-02 10:38:10] ab@php.net

Thanks for the report. It sounds very similar to bug #72451, which reports an issue with 7.0 and
Apache. If it's same, most likely the issues are in 7.0 already. However I was unable to
reproduce this with Apache, will try with Nginx yet. Best way were you to provide a stable way to
reproduce this, maybe it lays on a concrete script, some non core extension, or is catchable with
some specific server configuration.

Thanks.

------------------------------------------------------------------------


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

    https://bugs.php.net/bug.php?id=72729


--
Edit this bug report at https://bugs.php.net/bug.php?id=72729&edit=1


Thread (13 messages)

« previous php.bugs (#203164) next »