Bug #71466 SIGSEGV in libndbclient while using ClusterJ
Submitted: 24 Jan 2014 3:38 Modified: 4 Apr 2018 23:24
Reporter: Mike Cress Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Cluster/J Severity:S2 (Serious)
Version:7.3.3 OS:Any
Assigned to: MySQL Verification Team CPU Architecture:Any

[24 Jan 2014 3:38] Mike Cress 
Description:
Received the following error while using ClusteJ:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000115f79fde, pid=4225, tid=14855
#
# JRE version: 7.0_25-b15
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# [thread 16651 also had an error]
[thread 15623 also had an error]
[thread 23555 also had an error]
C  [libndbclient.6.0.0.dylib+0x53ffde]  _ZZL30print_cmdline_password_warningvE26password_warning_announced.b+0xd5dce

How to repeat:
Unknown.

Suggested fix:
Unknown.
[4 Apr 2018 0:56] MySQL Verification Team 
Hi,
the warning you are getting "print_cmdline_password_warningvE26password_warning_announced.b+0xd5dce" is about using password in command line. Not sure what's a bug here?

thanks
Bogdan
[4 Apr 2018 1:37] Mike Cress 
I submitted this over four years ago, so I no longer have any context with which to address your question.
[4 Apr 2018 1:40] Mike Cress 
I still wonder why a password error would generate a segmentation fault. I will assume by your response that this is the intended behavior for the library.
[4 Apr 2018 11:08] MySQL Verification Team 
Hi,

Actually you are right, it should not crash!

The issue here is that with latest "everything" I can't reproduce this, and with mixing old java and new mysql libs it will happen but nothing we can do about it.

Were you able to reproduce with latest?

all best
Bogdan
[4 Apr 2018 15:47] Mike Cress 
I no longer use this software, so I have no way of testing the issue.
[4 Apr 2018 23:24] MySQL Verification Team 
Hi,

Thanks. I can't reproduce this with latest libraries so it's fixed now. The issue you had was, I assume, when we introduced the warning in mysqlclient but not updated java libraries to handle that properly, but now it works ok so should be ok for anyone.

kind regards
Bogdan