Segfault with tx-rate option

[Raghavendra D Prabhu]

Running sysbench as

sysbench --test=./oltp.lua --db-driver=mysql --mysql-engine-trx=yes --mysql-table-engine=innodb --mysql-user=root --mysql-password=test --oltp-table-size=5000 --num-threads=8 --report-interval=1 --tx-rate=3 run

ended up segfaulting it.

(gdb) bt full
#0 eventgen_thread_proc (arg=<optimized out>) at sysbench.c:558
        pause_ns = <optimized out>
        next_ns = <optimized out>
        curr_ns = <optimized out>
        intr_ns = <optimized out>
        queue_array = <error reading variable queue_array (Cannot access memory at address 0x7ffff7c09fb0)>
        i = 0
#1 0x00007ffff76ece0f in start_thread () from /lib/libpthread.so.0
No symbol table info available.
#2 0x00007ffff6b1d04d in clone () from /lib/libc.so.6

The thread seems to be created at sysbench.c:790

[Raghavendra D Prabhu (raghavendra-prabhu)]

With --debug=on, --report-interval alone (with --tx-rate) is crashing.

raghu archie:/sysbench/sysbench/tests/db [300]% sysbench --debug=on --test=./oltp.lua --db-driver=mysql --mysql-engine-trx=yes --mysql-table-engine=innodb --mysql-user=root --mysql-password=test --oltp-table-size=5000 --num-threads=8 --report-interval=1 run sysbench 0.5: multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 8
Report intermediate results every 1 second(s)
Debug mode enabled.

Random number generator seed is 0 and will be ignored

DEBUG: Reporting thread started
DEBUG: Runner thread started (0)!
DEBUG: Runner thread started (1)!
DEBUG: Runner thread started (3)!
DEBUG: Runner thread started (2)!
DEBUG: Runner thread started (4)!
DEBUG: Runner thread started (6)!
Threads started!

DEBUG: Runner thread started (7)!
DEBUG: Runner thread started (5)!
zsh: segmentation fault sysbench --debug=on --test=./oltp.lua --db-driver=mysql --mysql-engine-trx=ye

But without --debug it works fine.

Backtrace: http://sprunge.us/aPGa

[Alexey Kopytov (akopytov)]

The crash with --debug=on appears to be a separate issue. Reported as bug #1043687.