Bug #78885 resolve_stack_dump is broken in 5.6 and up
Submitted: 20 Oct 2015 13:03 Modified: 29 Oct 2015 12:56
Reporter: Tor Didriksen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:5.6.28 OS:Any
Assigned to: CPU Architecture:Any

[20 Oct 2015 13:03] Tor Didriksen 
Description:
In MySQL 5.6 and up we use C++, which means there will be some long (mangled) symbol names.

How to repeat:
nm --numeric-sort --demangle  ../sql/mysqld > foo
$resolve_stack_dump -s foo -n var/log/mysqld.1.err 
resolve_stack_dump: sym table does not appear to be sorted, did you forget --numeric-sort arg to nm? trouble addr = 0xe, last = 0x9ef60d

Suggested fix:
Increase the size of some internal buffers.
[29 Oct 2015 12:56] Paul DuBois 
Bug affects no released version. No changelog entry needed.
[29 Oct 2015 13:15] Paul DuBois 
Correction: Noted in 5.6.8, 5.7.10, 5.8.0 changelogs.

Internal buffer sizes in resolve_stack_dump were increased to
accommodate larger symbol space requirements for C++ code.