A colleague of mine, Jaromir, provided a fixed patch and reproducible
test case. Please check the main stream bug report
http://bugs.php.net/bug.php?id=52389 for details
--
Segmentation fault in PHP5 with pgsql module
https://bugs.launchpad.net/bugs/607646
You received this bug notification becau
In the previous howto in step 2 please note there is no semicolon at the
end of the line after the change. This is correct!. On the following
line 1957 there is a function call that should be executed only if
ENGINE_add (toadd) returns true. If you keep the semicolon there the
code will compile but
It hasn't been fixed yet, unfortunately :-(
So here is a small howto for (k)ubuntu if you need to fix it (root
privileges assumed):
1) create a directory somewhere, e.g. /usr/src/openssl, chdir there and run:
apt-get source openssl
apt-get build-dep openssl
2) edit ./openssl-0.9.8k/debian/patche
Your welcome. I've submited the patch to PHP already, see
http://bugs.php.net/bug.php?id=52389 because we've detected this bug in
Mac and Windows as well.
** Bug watch added: bugs.php.net/ #52389
http://bugs.php.net/bug.php?id=52389
--
Segmentation fault in PHP5 with pgsql module
https://bugs
Greg Hanley: it seems the bug was found and will be fixed in the next
release of openssl. The reason why it is segfaulting on one machine and
not the other is probably the fact that one CPU supports AES-NI and the
other not. The problem is in multiple openssl initializations.
If you want to fix it
I think I've found the problem. It is in the pgsql extension. The memory
for the notices is allocated as non persistent but the whole structure
is persistent. The destructor tries to free memory that was already
cleaned by the garbage collector which causes the segmentation fault.
I've created a si
I tried recompile php without the suhosin patch and it is still
segfaulting.
See the *notice in frame #2 "address is out of bounds" (in function
_php_pgsql_notice_ptr_dtor)
This bug look very similar to php5 bug #542514 which was found in
5.2.10 and fixed in 5.2.11.
** Attachment added: "backt
It looks like something similar was already here one year ago...
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542514
** Bug watch added: Debian Bug tracker #542514
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542514
--
Segmentation fault in PHP5 with pgsql module
https://bugs.launchp
See openssl bug #2305
--
apache exit with signal Segmentation fault (11) on access to https:// if
php5-curl enabled
https://bugs.launchpad.net/bugs/590639
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
--
Ubuntu-serv
** Attachment added: "backtrace"
http://launchpadlibrarian.net/52202146/gdb-apache2_php.txt
--
Segmentation fault in PHP5 with pgsql module
https://bugs.launchpad.net/bugs/607646
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in
Public bug reported:
Binary package hint: php5
The apache exits with signal 11 Segmentation fault randomly (the same
request but a very complex php application, the backend can do different
things).
Program received signal SIGSEGV, Segmentation fault.
0x73d98343 in _zend_mm_free_canary_i
I checked it today and it is still there for me :-(
I checked the code and found that php5-curl in ext/curl/interface.c line
819 calls curl_global_init(CURL_GLOBAL_SSL). If I changed it to
CURL_GLOBAL_NOTHING the apache didn't crash. So I followed this code
through the libcurl to the openssl libra
I have the same configuration and also get the segmentation fault. I'd
like just to add that the apache crashes even if any SSL page is
accessed on that server, not only via php5-curl.
--
apache exit with signal Segmentation fault (11) on access to https:// if
php5-curl enabled
https://bugs.laun
13 matches
Mail list logo
