- Previous thread: FxCommo otra ventana abierta…FxCommo einem anderen Fenster geöffnet ...FxCommo open another window ...FxCommo aprire un'altra fi
- Next thread: LAST_INSERT_ID and CRC32
- Threads sorted by date: mysql 200905
Hello,
I have been using MySQL since months but I never had this error :
http://pastebin.com/f29be6e44
My functions where it happened (it's a function called by a thread) :
http://pastebin.com/f788ed68
It comes from this part :
port = result[numRow][1];
v6 = static_cast(result[numRow][2]);
session = static_cast(result[numRow][3]);
result[numRow][0].to_string(address);
I have been using MySQL since months but I never had this error :
http://pastebin.com/f29be6e44
My functions where it happened (it's a function called by a thread) :
http://pastebin.com/f788ed68
It comes from this part :
port = result[numRow][1];
v6 = static_cast(result[numRow][2]);
session = static_cast(result[numRow][3]);
result[numRow][0].to_string(address);
On May 2, 2009, at 6:04 AM, Martin Defeche wrote:
> I have been using MySQL since months but I never had this error :
> http://pastebin.com/f29be6e44
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
MySQL++.
> 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][1];
> v6 = static_cast(result[numRow][2]);
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.
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsub=bull@pubbs.net
> I have been using MySQL since months but I never had this error :
> http://pastebin.com/f29be6e44
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
MySQL++.
> 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][1];
> v6 = static_cast(result[numRow][2]);
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.
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsub=bull@pubbs.net
Related Threads
- linux-next: No Tree for November 3 - kernel
- [PHP] Free tech talk by Percona tonight in Palo Alto, CA - php
- [grails-dev] 1.2-SNAPSHOT show.gsp template error - grails
- [PHP] How to create CA certificate with PHP - php
- Creating a function dynamically - gcc
- [Red5] rtmp not working - osflash
- Is there any Spring Bean configuration which makes ActiveMQ consumer reconnects to server incase of fail over of Master node - activemq
- Fedora-release RPMS ? - fedora
- lockscreen/switch user issues - debian
- [gentoo-user] what is overloaded my X server? - gentoo
- Tomcat Https loadbalancing?? - tomcat
- [users@httpd] mod_proxy configuration issue - httpd