> With the code you cave me I ran gdb and made backtrace with option
> 'full' after the segmentation fault. Here is the result:
> (gdb) bt full
> #0 0x00000039d1068b85 in free () from /lib64/tls/libc.so.6
> No symbol table info available.
> #1 0x0000002a956d755e in my_no_flags_free () from
As you can see, it's barfing down in libc, via libmysqlclient. It's
quite possible that MySQL++ isn't at fault here. The program I sent you
doesn't crash here on our i386 boxen. As a result, it's going to be up
to you to find out where the problem is; again, it could just be that
MySQL++ is tickling a bug that's elsewhere in the system.
It seems you're running one of the transitional x64 systems. Such
systems often aren't as fully debugged as more stable systems, like i386
and the old guard of 64-bit systems.