Ankur G35 Saxena wrote:
>
> (gdb) bt
> #0 0x4025e276 in std::__default_alloc_template<true,
> 0>::allocate(unsigned) ()
> from /usr/lib/libstdc++.so.5
> #1 0x402642a8 in std::string::_Rep::_S_create(unsigned,
> std::allocator<char> const&) () from /usr/lib/libstdc++.so.5
> #2 0x402643d9 in std::string::_Rep::_M_clone(std::allocator<char>
> const&, unsigned) () from /usr/lib/libstdc++.so.5
> #3 0x40260e3d in std::string::_Rep::_M_grab(std::allocator<char>
> const&, std::allocator<char> const&) () from /usr/lib/libstdc++.so.5
> #4 0x40260f4c in std::string::string(std::string const&) ()
> from /usr/lib/libstdc++.so.5
It's clearly crashing deep in the Standard C++ library, not in MySQL++.
Therefore, either some piece of code corrupted it earlier, or it has a
thread bug of its own.
At this point, I would make sure that your program and _all_ of the
libraries it uses are built with thread-awareness. If you find no
problems there, run it under valgrind...hopefully you can catch this
problem at an earlier stage, instead of chasing secondary damage.
