Bug #2768 Segmentation fault
Submitted: 13 Feb 2004 1:23 Modified: 13 Feb 2004 1:49
Reporter: Claudia Nölker Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Administrator Severity:S1 (Critical)
Version:Alpha OS:Linux (Debian)
Assigned to: CPU Architecture:Any

[13 Feb 2004 1:23] Claudia Nölker
After changing the preferences (i.e. storing passwords cryptic), MySQL Administrator stops with a segmentation fault. 
gdb says:
(gdb) run
Starting program: /opt/mysql-administrator/bin/mysql-administrator
[New Thread 16384 (LWP 4121)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 4121)]
0x400cb617 in mallopt () from /lib/libc.so.6

Removing the entire directory and re-installing did not change anything.

How to repeat:
Probably by changing the values of the preferences. Can't test it anymore, because it crashes.

Suggested fix:
Perhaps there is a configuration file store somewhere outside of the installation directory which I can remove?
[13 Feb 2004 1:36] Claudia Nölker
After removing all the mysqlx_* files in .mysqlgui, it works again.

Saving the password in "Obscured" produces the segmentation fault.
Saving the password in plain format works.
The same if I choose "OS specific". But after the next start, the option is automagically changed to "Obscured", again! If I do not change anything, the Administrator works fine. But as soon as I "Apply Changes", it produces a segmentation fault at the next start of the program.
[13 Feb 2004 1:49] Ulrich Bayer
Thanks for reporting!
You are right saving the password in "Obscured" produces the bug.
"Os specific" encryption is not implemented yet.

This is identical to bug report 2764. So I will close this one.