Yes, that seems likely. I did some checking yesterday, and if I do the same
sequence of mysql_init(), mysql_options(), mysql_real_connect() calls as MySQL++
does, I get the same segmentation fault.
If I use other parameters to mysql_options(), or remove the call to
mysql_options(), I don't get the segmentation fault.
/Per Westermark
Per Westermark <pw...@teligent.se> writes:
Hi!
I am running Debian Woody too, and also gets segmentation fault in strcend().
Same gcc, MySQL++, mysql and same segmentation fault...
I remember getting a segfault
because of password parsing in .my.cnf,
Don't know if it occured if the pw was absent or present,
though.
Teligent AB, Tvistevägen 47, Box 7958, S-907 19 UMEÅ
Tel: +46 8 4101 7198