Bug #41612 resolve_stack_dump does not decode 5.1 stack trace
Submitted: 19 Dec 2008 3:05 Modified: 28 Jan 21:43
Reporter: Davi Arnaut
Status: Closed
Category:Server: General Severity:S3 (Non-critical)
Version:5.1,6.0 OS:Linux
Assigned to: Davi Arnaut Target Version:5.1+
Triage: Triaged: D3 (Medium)

[19 Dec 2008 3:05] Davi Arnaut 
Description:
resolve_stack_dump is not able to parse addresses passed in the new stack trace format
printed by 5.1

How to repeat:
resolve_stack_dump does not parse the following examples:

mysqld(_Z21mysql_execute_commandP3THD+0x41a0)[0x67a170] 
mysqld[0x7f1a5af000f0]
[0x6a8545]

Suggested fix:
resolve_stack_dump should look harder for a hexadecimal address.
[19 Dec 2008 11:47] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/62070

2742 Davi Arnaut	2008-12-19
      Bug#41612: resolve_stack_dump does not decode 5.1 stack trace
      
      resolve_stack_dump is not able to decode a stack trace produced
      by glibc's backtrace() functions. The problem is that the stack
      trace addresses are printed between brackets and the utility is
      not able to ignore the brackets.
      
      The solution is to modify resolve_stack_dump so it can recognize
      stack trace addresses surrounded by brackets. e.g. [0xdeadbeef].
[19 Dec 2008 14:28] Davi Arnaut 
Queued to 5.1-bugteam
[15 Jan 7:38] Bugs System 
Pushed into 5.1.31 (revid:joro@sun.com-20090115053147-tx1oapthnzgvs1ro) (version source
revid:azundris@mysql.com-20081230114838-cn52tu180wcrvh0h) (merge vers: 5.1.31) (pib:6)
[19 Jan 12:28] Bugs System 
Pushed into 5.1.31-ndb-6.2.17 (revid:tomas.ulin@sun.com-20090119095303-uwwvxiibtr38djii)
(version source revid:tomas.ulin@sun.com-20090115073240-1wanl85vlvw2she1) (merge vers:
5.1.31-ndb-6.2.17) (pib:6)
[19 Jan 14:06] Bugs System 
Pushed into 5.1.31-ndb-6.3.21 (revid:tomas.ulin@sun.com-20090119104956-guxz190n2kh31fxl)
(version source revid:tomas.ulin@sun.com-20090119104956-guxz190n2kh31fxl) (merge vers:
5.1.31-ndb-6.3.21) (pib:6)
[19 Jan 17:12] Bugs System 
Pushed into 5.1.31-ndb-6.4.1 (revid:tomas.ulin@sun.com-20090119144033-4aylstx5czzz88i5)
(version source revid:tomas.ulin@sun.com-20090119144033-4aylstx5czzz88i5) (merge vers:
5.1.31-ndb-6.4.1) (pib:6)
[20 Jan 19:58] Bugs System 
Pushed into 6.0.10-alpha (revid:joro@sun.com-20090119171328-2hemf2ndc1dxl0et) (version
source revid:azundris@mysql.com-20081230114916-c290n83z25wkt6e4) (merge vers:
6.0.9-alpha) (pib:6)
[28 Jan 21:43] Paul DuBois 
Noted in 5.1.31, 6.0.10 changelogs.

resolve_stack_dump was unable to resolve the stack trace format
produced by mysqld in MySQL 5.1 and up.
(See http://dev.mysql.com/doc/refman/5.1/en/using-stack-trace.html)