** Attachment added: "Diff for ext/pdo/pdo_sql_parser.c"
http://launchpadlibrarian.net/32455577/5.2.6.dfsg.1-3ubuntu4.2-5.2.10.dfsg.1-2ubuntu4-diff
--
apache2 crashed with SIGSEGV in pdo_parse_params()
https://bugs.launchpad.net/bugs/418220
You received this bug notification because you are
I traced the problem to a bug in ext/pdo/pdo_sql_parser.c that must have
been introduced somewhere around 5.2.6. I started working on a fix but
then thought to replace that file with one from a newer version of PHP.
I tried replacing with the one from 5.2.10.dfsg.1-2ubuntu4 and the bug
had already
I just built the pdo.so and pdo_mysql.so library files from the Ubuntu
source package by doing "apt-get -b source php5-mysql" and then copying
those 2 .so files to /usr/lib/php5/20060613 and restarted Apache. The
segmentation fault happened in the same way. This seems to indicate that
there was a b
I have been analyzing the differences between my Jaunty server which has
the segmentation fault problem, and a Jaunty virtual machine which works
fine. I've determined the key difference:
The problem machine has package php5-mysql (version
5.2.6.dfsg.1-3ubuntu4.2) installed. To eliminate the segme
I was able to get the test libmysqlclient15off package properly
installed and I tested with it and confirmed that that did fix the case
reported in bug 524366, BUT unfortunately it did not fix my bug as I've
reported here. It happens in the exact same way. So if it is actually
caused by the same bu
I am experiencing this bug in Jaunty.
I would like to try installing the Debian upstream replacement for
libmysqlclient15off as referenced in the bug:
http://ftp.fr.debian.org/debian/pool/main/m/mysql-
dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2+spu1_amd64.deb
I tried installing this with dpk
First of all, thank you so much for your help Ondrej! At this point I
think it is probably this bug. I tried running the test cases described
in the bug ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524366 )
from the CLI and indeed got a segmentation fault in the one other people
were getting
Hello Ondrej,
Thanks for the response. Yes, that line was from package php5-xdebug. I
had tried using that package to help track down the bug. I uninstalled
it and the crash still occurs in the same way, only the stacktrace now
doesn't include the xdebug part of course.
The bug is reproducible in
I've been investigating this and am not sure this is the same a Debian
bug 402181 as referenced above. That bug references Zend Optimizer,
which I am not using. My understanding is that the Zend Optimizer is a
binary program which is causing a conflict in that bug. The application
I am using is Zen
Public bug reported:
Binary package hint: apache2
This crash occurred in a PHP application that uses the Zend framework. I
can always make it crash but it will not crash consistently for the same
SQL call. Sometimes the idential call works fine and sometimes it causes
a crash. The application is
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/30744577/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/30744578/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/30744579/ProcStatus.txt
** Attachm
11 matches
Mail list logo
