Bug #21449 How to Resolve Stack Trace URL in MySQLD error log is incorrect
Submitted: 4 Aug 2006 13:41 Modified: 6 Oct 2006 3:11
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:all OS:Linux (Linux)
Assigned to: Iggy Galarza CPU Architecture:Any

[4 Aug 2006 13:41] Jonathan Miller
Description:
From a stach trace on 5.1 yesterday.
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

5.1
http://dev.mysql.com/doc/refman/5.1/en/using-stack-trace.html

5.0
http://dev.mysql.com/doc/refman/5.0/en/using-stack-trace.html

How to repeat:
N/A
[17 Aug 2006 0:59] Paul DuBois
The patch shouldn't use a version-specific URL.  Use the "generic"
form of the URL, which will redirect to the default manual.  This
will always resolve:

http://dev.mysql.com/doc/mysql/en/using-stack-trace.html

If the InnoDB source uses other URLs (I believe it does), they should be
converted similarly. I can provide assistance in mapping them to the
current URLs if needed.
[28 Sep 2006 17:58] 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/12753

ChangeSet@1.2289, 2006-09-28 13:58:53-04:00, iggy@rolltop.ignatz42.dyndns.org +1 -0
  Bug #21449 How to Resolve Stack Trace URL in MySQLD error log is incorrect.
[3 Oct 2006 20:01] Chad MILLER
Available in 5.0.26.
[3 Oct 2006 20:15] Chad MILLER
Available in 5.1.12-beta.
[6 Oct 2006 3:11] Paul DuBois
Noted in 5.0.26, 5.1.12 changelogs.

The URL into the online manual that is printed in the stack trace
message by the server was out of date. (Bug #21449)