某些操作系统上，错误日志中包含堆栈跟踪，如果mysqld意外崩溃。您可以使用该跟踪来确定mysqld崩溃的原因。请参阅第7.4.2节，“错误日志”。要获取堆栈跟踪，您必须不使用gcc编译mysqld，使用-fomit-frame-pointer选项。请参阅第7.9.1.1节，“编译 MySQL以供调试”。

错误日志中的堆栈跟踪可能如下所示：

mysqld got signal 11;
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 = 0x41fd0110 thread_stack 0x40000
mysqld(my_print_stacktrace+0x32)[0x9da402]
mysqld(handle_segfault+0x28a)[0x6648e9]
/lib/libpthread.so.0[0x7f1a5af000f0]
/lib/libc.so.6(strcmp+0x2)[0x7f1a5a10f0f2]
mysqld(_Z21check_change_passwordP3THDPKcS2_Pcj+0x7c)[0x7412cb]
mysqld(_ZN16set_var_password5checkEP3THD+0xd0)[0x688354]
mysqld(_Z17sql_set_variablesP3THDP4ListI12set_var_baseE+0x68)[0x688494]
mysqld(_Z21mysql_execute_commandP3THD+0x41a0)[0x67a170]
mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x282)[0x67f0ad]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xbb7[0x67fdf8]
mysqld(_Z10do_commandP3THD+0x24d)[0x6811b6]
mysqld(handle_one_connection+0x11c)[0x66e05e]

如果函数名解析失败，跟踪将包含较少信息：

mysqld got signal 11;
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 = 0x41fd0110 thread_stack 0x40000
[0x9da402]
[0x6648e9]
[0x7f1a5af000f0]
[0x7f1a5a10f0f2]
[0x7412cb]
[0x688354]
[0x688494]
[0x67a170]
[0x67f0ad]
[0x67fdf8]
[0x6811b6]
[0x66e05e]

较新的glibc堆栈跟踪函数还将打印地址相对于对象。在glibc-基于系统（Linux）上，插件中的意外退出跟踪可能如下所示：

plugin/auth/auth_test_plugin.so(+0x9a6)[0x7ff4d11c29a6]

要将相对地址（+0x9a6）转换为文件名和行号，请使用以下命令：

$> addr2line -fie auth_test_plugin.so 0x9a6
auth_test_plugin
mysql-trunk/plugin/auth/test_plugin.c:65

span class="command">addr2line工具是 Linux 上的binutils包的一部分。

在 Solaris 上，过程类似。Solaris 的printstack()已经打印相对地址：

plugin/auth/auth_test_plugin.so:0x1510

要转换，请使用以下命令：

$> gaddr2line -fie auth_test_plugin.so 0x1510
mysql-trunk/plugin/auth/test_plugin.c:88

Windows 已经打印地址、函数名和行号：

000007FEF07E10A4 auth_test_plugin.dll!auth_test_plugin()[test_plugin.c:72]