php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #44364 Access Violation when trying to access statement
Submitted: 2008-03-07 17:31 UTC Modified: 2008-03-28 01:00 UTC
From: johnw at litchfordgroup dot com Assigned: andrey (profile)
Status: No Feedback Package: MySQLi related
PHP Version: 5.2.5 OS: Windows 2003 Server
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: johnw at litchfordgroup dot com
New email:
PHP Version: OS:

 

 [2008-03-07 17:31 UTC] johnw at litchfordgroup dot com 
Description:
------------
I am trying to take advantage of OOP, I have one function that I can pass a sql query to and parameters to bind to. The function should return the statement object so I can then use it in the calling functon.

In the example, I am using a global variable to the class. I would rather the function return the statement object but I was getting this same error. So I tried it as a global variable with no luck.

Reproduce code:
---------------
http://www.litchfordgroup.com/example.txt

Expected result:
----------------
returns statement object so that I can bind the results and access the values.

Actual result:
--------------
PHP has encountered an Access Violation at 0F18165A

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2008-03-07 17:39 UTC] felipe@php.net 
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32

Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.
 [2008-03-07 21:46 UTC] johnw at litchfordgroup dot com 
I cannot get this debug to work. I followed the steps in your link. The instructions are missing a step (see screen 4 below).

Everything seems to be setup right, but when I run the php file that fails, it does nothing.
 [2008-03-07 21:46 UTC] johnw at litchfordgroup dot com 
Here are the screen shots of my debugging tool configuration.

http://www.litchfordgroup.com/screen1.jpg
 [2008-03-07 21:47 UTC] johnw at litchfordgroup dot com 
http://www.litchfordgroup.com/screen2.jpg
http://www.litchfordgroup.com/screen3.jpg
 [2008-03-07 21:47 UTC] johnw at litchfordgroup dot com 
http://www.litchfordgroup.com/screen4.jpg
http://www.litchfordgroup.com/screen5.jpg
http://www.litchfordgroup.com/screen6.jpg
 [2008-03-08 20:24 UTC] johnw at litchfordgroup dot com 
Please provide an update on performing the backtrace. This issue is preventing me from moving forward on my project.
 [2008-03-10 16:26 UTC] johnw at litchfordgroup dot com 
Seriously a reply would be much appreciated!
 [2008-03-20 16:14 UTC] andrey@php.net 
You are using bind_param in a wrong way. Every call to bind_param() unbinds the previous variables. Thus all parameter variables to be bound should be bound in one call to bind_param. The same is valid also for bind_result. In your case it doesn't matter much, as you have only one parameter.
Can you provide that pr_get_list_data() function from mysql. If it contains private information you can send it over email to my address and I try to reproduce the problem.

Thanks,
Andrey
 [2008-03-28 01:00 UTC] php-bugs at lists dot php dot net 
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Dec 21 12:01:31 2024 UTC