MySQL crashes under VTune 2.0

[vadim2]

MySQL crashes under VTune 2.0

1. I run

vtl activity -c callgraph -app /usr/local/mysql/libexec/mysqld,--user=mysql -moi /usr/local/mysql/libexec/mysqld run

2. Then mysqladmin shutdown

Result:

mysqld got signal 11;
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.

key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
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...
Cannot determine thread, fp=0xbfffd678, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80cedda
0x40078a65
0x40044237
0x4001fc31
0x4002010d
0x40021a24
0x4002d34e
0x4000df32
0x4020053b
0x401978b6
0x7fbd309
0x401955d6
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Without VTune MySQL works fine .

--
Vadim Tkachenko, Support Engineer
MySQL AB, www.mysql.com

[David_A_Intel1]

Thanks, Vadim. Is MySQL already running when you invoke this vtl command? Call Graph is a very intrusive form of profiling data collection. It literally modifies the binary prior to running it. You typically cannot use Call Graph on daemons, and definitely not on kernel modules.

Just as a reminder, if you would like to report a problem please submit an issue at Intel Premier Support. The forums is for discussioning tips and techniques among other users.

Regards,