DrizzleLock segment fault

Bug #680028 reported by Andrew Hutchings
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
High
Brian Aker
7.0
Fix Released
High
Brian Aker

Bug Description

* Updated with easier way to reproduce

mysql1> flush tables with read lock;
mysql2> select * from t1 for update;

Now ctrl-c mysql2. Drizzled segfault.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdf9a3710 (LWP 21869)]
reset (mysql_lock=0x7fffdf9a24f8) at drizzled/locking/global.cc:170
170 (*iter)->type= TL_UNLOCK;
(gdb) bt
#0 reset (mysql_lock=0x7fffdf9a24f8) at drizzled/locking/global.cc:170
#1 drizzled::reset_lock_data_and_free (mysql_lock=0x7fffdf9a24f8)
    at drizzled/locking/global.cc:161
#2 0x00000000005f87ba in drizzled::Session::lockTables (
    this=<value optimised out>, tables=0x1870348, count=<value optimised out>,
    flags=<value optimised out>, need_reopen=<value optimised out>)
    at drizzled/locking/global.cc:245
#3 0x00000000006588d7 in drizzled::Session::lock_tables (this=0x186a520,
    tables=<value optimised out>, count=<value optimised out>,
    need_reopen=0x7fffdf9a25af) at drizzled/sql_base.cc:1808
#4 0x000000000064bd74 in drizzled::Session::openTablesLock (this=0x186a520,
    tables=0x1870118) at drizzled/session.cc:1934
#5 0x00000000006717c1 in drizzled::execute_sqlcom_select (session=0x186a520,
    all_tables=0x1870118) at drizzled/sql_parse.cc:507
#6 0x0000000000673f85 in mysql_execute_command (session=0x186a520,
    inBuf=<value optimised out>, length=27) at drizzled/sql_parse.cc:480
#7 drizzled::mysql_parse (session=0x186a520, inBuf=<value optimised out>,
    length=27) at drizzled/sql_parse.cc:752
#8 0x0000000000674a80 in drizzled::dispatch_command (
    command=<value optimised out>, session=0x186a520,
    packet=<value optimised out>, packet_length=<value optimised out>)
    at drizzled/sql_parse.cc:228
#9 0x000000000064b34a in drizzled::Session::executeStatement (this=0x186a520)
    at drizzled/session.cc:710
#10 0x0000000000652347 in drizzled::Session::run (this=0x186a520)
    at drizzled/session.cc:549
#11 0x00007ffff174711e in MultiThreadScheduler::runSession (this=0x1843970,
    id=1) at plugin/multi_thread/multi_thread.cc:61
#12 0x00007ffff6b698e0 in thread_proxy ()
   from /usr/lib/libboost_thread.so.1.44.0
#13 0x00007ffff543d971 in start_thread (arg=<value optimised out>)
    at pthread_create.c:304
#14 0x00007ffff519994d in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#15 0x0000000000000000 in ?? ()

summary: - transaction crash
+ DrizzleLock segment fault
Changed in drizzle:
importance: Undecided → High
description: updated
Revision history for this message
Brian Aker (brianaker) wrote :

Doing a bisect.

Revision history for this message
Brian Aker (brianaker) wrote :

Crash is not found in revision 1800, but is found in 1900.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.