Bug #8952 Segfault executing "SELECT 1"
Submitted: 4 Mar 2005 18:35 Modified: 7 Mar 2005 19:04
Reporter: [ name withheld ] Email Updates:
Status: Closed Impact on me:
Category:MySQL Query Browser Severity:S2 (Serious)
Version:1.1.6 OS:Linux (Linux/Debian)
Assigned to: Alfredo Kojima CPU Architecture:Any

[4 Mar 2005 18:35] [ name withheld ]
This is a followup for #8301. (I can't add a comment there - bug system problems).

I can still reproduce this problem.

SELECT 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1

(gdb) bt
#0  0xb6e39d03 in strchr () from /lib/tls/libc.so.6
#1  0x0817b438 in s_query_set_params ()
#2  0x08173a05 in myx_query_execute ()
#3  0x080ac33c in MQQueryDispatcher::QueryRequest::execute ()
#4  0x080af5bb in MQQueryDispatcher::normal_thread ()
#5  0x080b2675 in SigC::ClassSlot1_<void, MQQueryDispatcher::Request*, MQQueryDispatcher>::proxy ()
#6  0x080b26b9 in SigC::AdaptorBindSlot0_1_<void, MQQueryDispatcher::Request*>::proxy ()
#7  0xb71db766 in (anonymous namespace)::call_thread_entry_slot () from /usr/lib/libglibmm-2.0.so.1
#8  0xb70207fd in g_static_private_free () from /usr/lib/libglib-2.0.so.0
#9  0xb779ab63 in start_thread () from /lib/tls/libpthread.so.0
#10 0xb6e9ac4a in clone () from /lib/tls/libc.so.6

Clicking the the "Execute" button doesn't do it this time. But hitting Ctrl+Enter repeatedly will trigger the bug.

I also found that if you hold Ctrl+Enter key down, the program seems to freeze completely.

How to repeat:
[7 Mar 2005 19:04] Alfredo Kojima
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

The crash happened when a new query was dispatched before the previous one could be finished, in the same tab. It has been fixed, but you can workaround it until the next release by waiting QB to become idle before executing again.

As always, thanks for the report.