MySQL Bugs: #53537: NDBFS block has jam()s in multiple source files without trace line offset

Bug #53537	NDBFS block has jam()s in multiple source files without trace line offset
Submitted:	10 May 2010 11:19	Modified:	31 Dec 2010 19:42
Reporter:	Hartmut Holzgraefe	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	mysql-5.1-telco-6.3, mysql-5.1-telco-7.1	OS:	Any
Assigned to:		CPU Architecture:	Any
Triage:	Triaged: D4 (Minor) / R1 (None/Negligible) / E2 (Low)

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
The NDBFS block has jam() and jamEntry() calls in both Ndbfs.cpp and VoidFs.cpp but does not set a trace line offset for either file (like it is done in e.g. DBTUP) so that this can lead to ambiguous trace entries

How to repeat:
check source

Suggested fix:
add an offset to jam()s in VoidFs.cpp

Thank you for the report.

Verified as described.