On May 2, 2009, at 6:04 AM, Martin Defeche wrote:
> I have been using MySQL since months but I never had this error :
That shows a double memory free, certainly a bug, but it doesn't show
libmysql++*.so in the call stack, so I don't see why you're blaming
> it's a function called by a thread
Have you followed all of the advice in the chapter on threads in the
user manual? If not, it's quite possible to make MySQL++ or MySQL
corrupt memory through double frees or other mechanisms.
> port = result[numRow];
> v6 = static_cast<bool>(result[numRow]);
These casts really shouldn't be needed. I doubt it's the source of
your current problem, but it does suggest that you're mixing types
where you shouldn't.
|• Weird Error||Martin Defeche||2 May|
| • Re: Weird Error||Warren Young||2 May|