Bug #11749 No message slogan found for Signal 8 received. (need better message)
Submitted: 5 Jul 2005 20:49 Modified: 13 Oct 2005 11:18
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1-> OS:Linux (Linux)
Assigned to: Tomas Ulin CPU Architecture:Any

[5 Jul 2005 20:49] Jonathan Miller
A better message is needed for when an error such as this is captured.

Date/Time: Tuesday 5 July 2005 - 22:32:02
Type of error: error
Message: No message slogan found
Fault ID: 0
Problem data: Signal 8 received
Object of reference: main.cpp
ProgramName: /home/ndbdev/jmiller/builds/libexec/ndbd
ProcessID: 10707
TraceFile: /space/run/ndb_5_trace.log.4
Version 5.1.0 (a_drop5p3)

How to repeat:
Not sure. Check bug 11747

Suggested fix:
A better message is needed for when an error such as this is captured. I might be good to add the calling function that caused/caught the error.
[6 Jul 2005 3:19] Jorge del Conde
While I couldn't get ndb to throw a signal 8, i was unable to find the slogan in the 5.0bk source code
[12 Jul 2005 14:59] Tomas Ulin
Best thing we can do is to print a text corresponding to the signal...

in this case "Floating point exception" which is "Signal 8"

keeping track of function would be too expensive...
[5 Oct 2005 12:38] 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:

[10 Oct 2005 6:08] Tomas Ulin
Bug #13197, Bug #11749, Bug #12786, Bug #11739

New and improved Error messages from 5.0.15.  Error messages not updated in 4.1.
[13 Oct 2005 11:18] Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Documented in 5.0.15 changelog. Closed.