Assertion failure on set_eof_status from ha_show_status

Bug #1043620 reported by Raghavendra D Prabhu on 2012-08-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server
Status tracked in 5.7

Bug Description

While testing for bug 1040735, I hit the assertion on a UNIV_DEBUG enabled binary:

mysqld: /media/Vone/percona-server/origin/Percona-Server/sql/ void Diagnostics_area::set_eof_status(THD*): Assertion `! is_set()' failed.
16:38:30 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Please help us make Percona Server better by reporting any
bugs at

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 21948348 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x4605c40
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f20d7efae68 thread_stack 0x40000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f20d8008010): is an invalid pointer
Connection ID (thread ID): 14220

You may download the Percona Server operations manual by visiting You may find information
in the manual which will help you identify the cause of the crash.

It seemed to have hit:

DBUG_ASSERT(! is_set()); in my_eof

called from

if (!result)
    my_eof(thd); in ha_show_status.

There are couple of related upstream bugs (some of them fixed)

but they are hit under different contexts.

Also, not sure if related to but I disabled the assertion temporarily since I was hitting it consistently to look for point where 1040735 was failing.

Raghu, Stewart -

Do you have a repeatable testcase for this?

Laurynas Biveinis <email address hidden> writes:
> Raghu, Stewart -
> Do you have a repeatable testcase for this?

I got it to hit with a mysqlslap worload as well as one repeatedly
running some DDL and SHOW INNODB STATUS (the C test case for MySQL bug
.... )

Stewart Smith

I hit it under similar circumstance -- when running sysbench and C test case of bug 60682 (with around 50 threads (needs to be changed in source), the test case runs 'show engine innodb status' a lot).

Needs to be re-verified

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

Other bug subscribers