Bug #39988 Meaningful stack trace on Solaris
Submitted: 12 Oct 2008 14:33 Modified: 1 Feb 2010 12:26
Reporter: Davi Arnaut (OCA) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: General Severity:S4 (Feature request)
Version:5.1 OS:Solaris
Assigned to: Assigned Account CPU Architecture:Any

[12 Oct 2008 14:33] Davi Arnaut 
Description:
Currently, when the MySQL server crashes on Solaris, the generated stack dump is numeric and needs external tools to properly resolve the functions names. The problem is that this is not very helpful to someone who has a limited knowledge of debugging techniques.

Nowadays, Solaris 9 and later provides a function called printstack which enables the runtime to print symbolic (meaningful) stack traces if something goes wrong.

How to repeat:
See a MySQL stack trace on Solaris 9.

Suggested fix:
Implement MySQL stacktrace using Solaris's printstack() function.
[13 Oct 2008 13:43] Davi Arnaut 
On Solaris 9 sparc it's even worse with mysql-5.1 as there is no stack trace at all.
[1 Feb 2010 12:26] Staale Smedseng 
Closed as duplicate of Bug#47391.