Hi all,
I recently installed 5.4.0 on a CentOS 6.2 box and am now getting
segfaults anytime we try to draw a PDF file (with fpdf). My config line
is below:
./configure --with-apxs2=/usr/sbin/apxs --enable-cli --enable-exif
--enable-mbstring --enable-mbregex --enable-sockets --with-mysql
--w
On 4/17/12 7:29 AM, Joseph Koenig wrote:
Hi all,
I recently installed 5.4.0 on a CentOS 6.2 box and am now getting segfaults
anytime we try to draw a PDF file (with fpdf). My config line is below:
./configure --with-apxs2=/usr/sbin/apxs --enable-cli --enable-exif
--enable-mbstring --enable-
On 4/17/12 10:34 AM, Christopher Jones wrote:
On 4/17/12 7:29 AM, Joseph Koenig wrote:
Hi all,
I recently installed 5.4.0 on a CentOS 6.2 box and am now getting
segfaults anytime we try to draw a PDF file (with fpdf). My config
line is below:
./configure --with-apxs2=/usr/sbin/apxs --en
On 04/17/2012 10:18 AM, Joseph Koenig wrote:
Installed it about a week and a half ago. Removing APC did nothing to fix the
issue. Bug #61757 filed.
Thanks!
Joe Koenig
Creative Anvil
I would really, really encourage you to put a complete testcase in the
bug. The PHP core developers simply
On 4/17/12 12:33 PM, Christopher Jones wrote:
On 04/17/2012 10:18 AM, Joseph Koenig wrote:
Installed it about a week and a half ago. Removing APC did nothing to
fix the issue. Bug #61757 filed.
Thanks!
Joe Koenig
Creative Anvil
I would really, really encourage you to put a complete testc
On 04/17/2012 11:47 AM, Joseph Koenig wrote:
Chris
Thanks for the feedback. I'm not 100% sure where to go with the
testcase because if I pull out those 10 or so lines of code. I'm not
necessarily getting the segfault, but by the same token, those 10
lines of code are definitely causing the i
On 4/17/12 2:15 PM, Christopher Jones wrote:
On 04/17/2012 11:47 AM, Joseph Koenig wrote:
In general you could:
- Try the latest PHP 5.4 snapshot. Who knows, maybe a fix has already
been merged?
- remove any unnecessary extensions to eliminate them as culprits.
- keep trying to simplify t
On 04/17/2012 01:26 PM, Joseph Koenig wrote:
Thanks again Chris. Same problem exists with the latest 5.4, so I
built with --enable-debug and added a backtrace to the bug report as
well as the fact that 5.3.10 does not produce the same issue. Will
work on stripping down our original code to prov
