Crash due to missing DBUG_RETURN

[Raghavendra D Prabhu]

While running mysql-debug --debug --user=mysql and shutting down server, I noticed

mysqld-debug: debugger aborting because missing DBUG_RETURN or DBUG_VOID_RETURN macro in function "?func"

11:59:18 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 http://bugs.percona.com/

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

Thread pointer: 0x7f6778000a00
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 = 7f678c316e88 thread_stack 0x40000
mysqld-debug(my_print_stacktrace+0x35)[0x7fbde5]
mysqld-debug(handle_fatal_signal+0x305)[0x6c3939]
/lib64/libpthread.so.0[0x37e3c0f500]
/lib64/libc.so.6(gsignal+0x35)[0x37e38328a5]
/lib64/libc.so.6(abort+0x175)[0x37e3834085]
mysqld-debug[0xa0ca02]
mysqld-debug(_db_return_+0x86)[0xa0dbcb]
mysqld-debug(start_wsrep_THD+0x755)[0x525f0e]
/lib64/libpthread.so.0[0x37e3c07851]
/lib64/libc.so.6(clone+0x6d)[0x37e38e811d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 2
Status: KILL_CONNECTION

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.

========================================================

I presume this is because DBUG_RETURN is missing in start_wsrep_THD (or one of its callees)