Description:
A similar bug was fixed before, but it has cropped up again. Whenever I hit the explain button after executing a query, a segfault happens. The gdb backtrace is below:
(gdb) bt
#0 0x0830da4c in free_root ()
#1 0x0831ba94 in free_old_query ()
#2 0x0831dbe1 in mysql_close ()
#3 0x082db8e5 in myx_mysql_close (mysql=0x90927a4) at myx_library.c:453
#4 0x081fe143 in MQQueryDispatcher::normal_thread(MQQueryDispatcher::Request*) (
this=0x9007048, req=0x90912a0) at MQQueryDispatcher.cc:302
#5 0x08201845 in SigC::ClassSlot1_<void, MQQueryDispatcher::Request*, MQQueryDispatcher>::proxy(MQQueryDispatcher::Request* const&, void*) (p1=@0x9091a5c, s=0x9090570)
at class_slot.h:112
#6 0x08201880 in SigC::AdaptorBindSlot0_1_<void, MQQueryDispatcher::Request*>::proxy(void*) (data=0x9091a38) at bind.h:153
#7 0x085a08c6 in (anonymous namespace)::call_thread_entry_slot(void*) ()
#8 0x406a18bc in g_static_private_free () from /usr/lib/libglib-2.0.so.0
#9 0x00000006 in ?? ()
Previous frame inner to this frame (corrupt stack?)
How to repeat:
I am connecting to a MySQL Server 4.0.20 running on FreeBSD 4.8.
Run program, switch default schema to some database. Type in a query and hit EXECUTE. The results will show up (I had it segfault at that point once as well). Then, hit the EXPLAIN button. It will then segfault.
Suggested fix:
No idea