#33283 [Opn]: Apache GPF's when attempting to use PDO
| From: | david dot prusak at copart dot com | Date: | Fri, 10 Jun 2005 16:39:17 +0000 |
| Subject: | #33283 [Opn]: Apache GPF's when attempting to use PDO | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-80134@lists.php.net to get a copy of this message | ||
ID: 33283
User updated by: david dot prusak at copart dot com
Reported By: david dot prusak at copart dot com
Status: Open
Bug Type: PDO related
Operating System: Windows XP
PHP Version: 5.0.4
New Comment:
Well, I installed all this on my solaris box. Accessing the same page,
I get this in my apache error.log
[Fri Jun 10 09:29:03 2005] [notice] child pid 19516 exit signal
Segmentation fault (11)
Removing the "prepare" doesn't segfault apache. The behavior is
identical to the windows version.
Previous Comments:
------------------------------------------------------------------------
[2005-06-10 17:22:03] david dot prusak at copart dot com
No, adding that didn't stop the GPF, sorry.
------------------------------------------------------------------------
[2005-06-09 23:59:47] wez@php.net
If you add:
$stmt = null;
$dbh = null;
to the end of your script, does the segfault go away?
------------------------------------------------------------------------
[2005-06-09 21:26:39] david dot prusak at copart dot com
Oops sorry about that.
This fails with a gpf:
<?php
try {
$dbh = new PDO('odbc:DATABASE', 'USER', 'PASS')
$stmt = $dbh->prepare("SELECT * FROM TABLE");
} catch (Exception $e) {
echo "Failed: " . $e->getMessage();
}
?>
While this works just fine and prints "Connected",
<?php
try {
$dbh = new PDO('odbc:DATABASE', 'USER', 'PASS')
print "Connected\n";
} catch (Exception $e) {
echo "Failed: " . $e->getMessage();
}
?>
When I use exec, I don't get the GPF, but I'm also not getting the
correct results. When trying to query a fake table, I don't get an
error. When I query the correct table, I don't get a count.
When I put in an incorrect database, user or password, I do get the
correct error. So that tells me that I can connect to the database.
<?php
try {
$dbh = new PDO('odbc:DATABASE', 'USER', 'PASS')
print "Connected<br>";
$count = $dbh->exec("SELECT * FROM FAKETABLE");
print "Count: $count";
} catch (Exception $e) {
echo "Failed: " . $e->getMessage();
}
?>
I did verify the php.ini is correct. I put in a typo in the ini file
to see if Apache will err on start up and it did. (brute force method
:) )
Hope that's not too much information.
--David
------------------------------------------------------------------------
[2005-06-09 19:39:53] wez@php.net
Sounds like two different issues, neither of which is PDO specific ;-)
Check that you were modifying the right php.ini file, and that you
restarted apache after changing it. (phpinfo() will help you to figure
that out).
Your script is broken, btw. You catch the exception, effectively
ignoring the error, and then continue to use the $dbh even though you
"know" it isn't there. You should move that code inside the try {}
block, just after you echo "Connected";
The GPF concerns me, but I suspect it will go away once you load PDO
correctly. If you're feeling motivated, can you try pruning down your
script to the smallest possible test case that reproduces the GPF? I'm
hoping you can cut it down to something like this:
<?php
class foo {
function __construct() {
throw new Exception("bang");
}
}
try {
$foo = new foo;
} catch (Exception $e) {
echo "Failed " . $e->getMessage();
}
$foo->bar();
?>
------------------------------------------------------------------------
[2005-06-09 19:10:13] david dot prusak at copart dot com
Might want to ingore the gdb information I provided. It's not correct
on the windows system. I more than happy to help debug. Just let me
know what you need and how I can get it to you.
Thanks,
--David
------------------------------------------------------------------------
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
http://bugs.php.net/33283
--
Edit this bug report at http://bugs.php.net/?id=33283&edit=1