Bug #70392 [Fbk]: SIGSEGV during PHP shutdown

From: Date: Wed, 02 Sep 2015 10:09:19 +0000
Subject: Bug #70392 [Fbk]: SIGSEGV during PHP shutdown
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-195692@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=70392&edit=1

 ID:                 70392
 Updated by:         dmitry@php.net
 Reported by:        pegasus at vaultwiki dot org
 Summary:            SIGSEGV during PHP shutdown
 Status:             Feedback
 Type:               Bug
 Package:            *General Issues
 Operating System:   Centos 7 64-bit
 PHP Version:        7.0Git-2015-08-30 (Git)
 Assigned To:        dmitry
 Block user comment: N
 Private report:     N

 New Comment:

Please check the latest git version.
The following commit might fix the problem.

http://git.php.net/?p=php-src.git;a=commitdiff;h=111bd5d8c45a9c44b2e39951e6a1a543a893f8bd


Previous Comments:
------------------------------------------------------------------------
[2015-09-01 17:27:25] dmitry@php.net

p dbg
p bin_num

------------------------------------------------------------------------
[2015-08-31 18:09:06] pegasus at vaultwiki dot org

How would I output the value?

------------------------------------------------------------------------
[2015-08-31 16:30:35] dmitry@php.net

The crash on line "if (dbg->size != 0)" is possible only when "dbg" is
invalid.
The crash occured on processing 25-th element of 510-th page.
We allocate 512 pages at once. So I assume "dbg" somehow points into page after 512.

I don't see how this may happen yet.

Can you show the values of "dbg" and "bin_num"?

------------------------------------------------------------------------
[2015-08-31 13:55:31] laruence@php.net

Dmitry, can you see anything useful here?

------------------------------------------------------------------------
[2015-08-31 13:43:36] laruence@php.net

hmm, we can not do something useful here if you don't have a way to reproduce it :<

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


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=70392


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


Thread (13 messages)

« previous php.bugs (#195692) next »