Bug #75737 NDB Debugger doesn't have gsn 463 name

• Submitted: 3 Feb 2015 3:33
• Modified: 4 Jun 2015 21:37
• Reporter: Stewart Smith
• Status: Can't repeat
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• Version: 7.3.8
• OS: Any
• Assigned to: MySQL Verification Team
• CPU Architecture: Any

[3 Feb 2015 3:33] Stewart Smith

Description:
While poking at NDB on POWER8, I got a crash where looking at the trace log I noticed the following:

--------------- Signal ----------------
r.bn: 254 "CMVMI", r.proc: 1, r.sigId: -1993536586 gsn: 463 "Unknown" prio: 1
s.bn: 266/1 "TRPMAN", s.proc: 1, s.sigId: 508 length: 1 trace: 8 #sec: 0 fragInf: 0
 H'00000004

Unknown should be CANCEL_SUBSCRIPTION_REQ according to storage/ndb/include/kernel/GlobalSignalNumber.h

How to repeat:
Be lucky, have a crash with the right signal in the buffer

Suggested fix:
Apply my patch!

[3 Feb 2015 3:34] Stewart Smith

Add name for signal 463

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: ndb-signal-name-463.patch (text/x-patch), 658 bytes.

[5 Mar 2015 11:12] Mikael Ronström

This issue was fixed as part of 7.4 development, so the fix exists in the 7.4 tree.

[4 Jun 2015 8:45] MySQL Verification Team

Hi Stewart,

Can't locally reproduce but the source shows the bug exist. No plans to fix it in pre 7.4. 

It is fixed in 7.4

kind regards
Bogdan Kecman

[4 Jun 2015 21:37] Stewart Smith

That's fine, glad to see it's fixed and that somebody looks at bugs :)