I've done some more investigation on this by executing python interactively and here are my results:
1) Using MySQLdb
MySQLdb is imported and a simple query issued against a database by connect(), creating a cursor and doing an execute() of the SQL query.
The pointer to wrong page message is output at completion of the execute() call.
2) Using _mysql
_mysql is imported and the same simple query issued against a database by connect(), query(), store_result() and fetch_row().
The pointer to wrong page message is output when exiting from python after completion of the fetch_row() call.
I'm pretty certain my python installation is OK. It runs mailman and I haven't seen any of these messages in the cron logs.
I've found references to these messages on the FreeBSD mailing list archives. All of them appear to be application caused errors due to memory and/or pointer corruption.
Could this problem be located in _mysql.so?
Regards,
Neil Darlow.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I've just built and installed py-MySQLdb-0.9.0 on FreeBSD-4.2 running python-2.1.
I am trying some of the examples described in MySQLdb.html and am finding that I get a warning whenever I invoke the cursor's execute method e.g.:
python in free(): warning: pointer to wrong page.
The queries seem to execute OK and the cursor fetchone method returns the expected data. What does this warning mean?
Regards,
Neil Darlow.
I've done some more investigation on this by executing python interactively and here are my results:
1) Using MySQLdb
MySQLdb is imported and a simple query issued against a database by connect(), creating a cursor and doing an execute() of the SQL query.
The pointer to wrong page message is output at completion of the execute() call.
2) Using _mysql
_mysql is imported and the same simple query issued against a database by connect(), query(), store_result() and fetch_row().
The pointer to wrong page message is output when exiting from python after completion of the fetch_row() call.
I'm pretty certain my python installation is OK. It runs mailman and I haven't seen any of these messages in the cron logs.
I've found references to these messages on the FreeBSD mailing list archives. All of them appear to be application caused errors due to memory and/or pointer corruption.
Could this problem be located in _mysql.so?
Regards,
Neil Darlow.