Patrick Galbraith wrote:
Federico Giannici wrote:
Federico,
Hmm One of the problems I had is that I didn't have a Open BSD box
to test this out. Perhaps your second suggestion might be a solution to
pursue. I would prefer that the argument to mysql_st_internal_execute
take one type
Patrick Galbraith wrote:
Sam Smith wrote:
Sam,
Thanks for the trace. I need to talk to someone about getting an OpenBSD
box to test out potential solutions.
I'm available to test a prerelease version of the DBD driver.
Bye.
--
___
__
() is used in only two places. Instead of
doing all that tests at the beginning of the function to handle both
cases (STH and DBH for the h parameter), why don't you change the type
of the first parameter into a imp_dbh? Wouldn't everything be clearer
this way?
Bye.
Federico Giannici wrote:
Hi
encountered this issue in other parts of
the driver. There is a better way to do this, and I can look at making
sure what is being passed is the same data object.
Thanks!
Patrick
Federico Giannici wrote:
Since there has been no reply to my previous message, I have done
further investigations
irrelevant.
Federico Giannici wrote:
It seems to me that there is some kind of memory access problem with DBI
or DBD-Mysql.
I'm using OpenBSD 3.9-stable amd64. On OpenBSD 3.3 i386 the problem
didn't appeared. As you may know, recent version of OpenBSD have a new
kind of memory handling that make
It seems to me that there is some kind of memory access problem with DBI
or DBD-Mysql.
I'm using OpenBSD 3.9-stable amd64. On OpenBSD 3.3 i386 the problem
didn't appeared. As you may know, recent version of OpenBSD have a new
kind of memory handling that make the programs segfault when they
