Bug #58267 | MySQL Client crashes when entering ^s^d^c (ctrl-s ctrl-d ctrl-c / c-s c-d c-c). | ||
---|---|---|---|
Submitted: | 17 Nov 2010 18:48 | Modified: | 15 May 2013 16:41 |
Reporter: | Michael Clark | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 5.5.30 | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | client, crash, linux, windows? |
[17 Nov 2010 18:48]
Michael Clark
[17 Nov 2010 20:51]
Peter Laursen
Also on Windows it crashes!
[18 Nov 2010 15:24]
Valeriy Kravchuk
Please, check if this happens with a newer version of client, from MySQL 5.0.91.
[18 Nov 2010 15:47]
Peter Laursen
@Valeriy: I tried 5.1.52. Wouldn't it be pretty simple to check for yourself? It is 6 keystrokes only!
[18 Nov 2010 17:20]
Michael Clark
Worked on 5.1.51 on ArchLinux. $mysql --version mysql Ver 14.14 Distrib 5.1.51, for unknown-linux-gnu (x86_64) using readline 6.1 For consistency, on Ubuntu LTS: $mysql --version mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2
[18 Nov 2010 17:40]
Valeriy Kravchuk
Peter, Do you really think that I had NOT checked? I've check with 5.1.52 on Windows XP (no crash), 5.1.54 on Ubuntu 10.04 and 5.1.54 on Mac OS X. No crash or any problem on these platforms for me. That's why I ask. If you prefer me to just ignore bug reports that I can not repeat, I can surely do so.
[18 Nov 2010 18:19]
Peter Laursen
I tried again with client shipped with Win7/64 5.0.90 + 5.1.52 + 5.5.7 servers. They all crash for me.
[18 Nov 2010 18:43]
Peter Laursen
Actually I think 'crash' is not the right term. I noticed the string 'Bye' shortly before the client window crashes (using the client icon from Windows startmenu). When explicitly starting 'mysql' from cmd.exe the client window does not close: C:\Users\Peter>cd \program files\mysql\mysql server 5.1\bin C:\Program Files\MySQL\MySQL Server 5.1\bin>mysql -uroot -p Enter password: ******** Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 3 Server version: 5.1.52-community MySQL Community Server (GPL) Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved. This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL v2 license Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> Bye Ctrl-C -- exit! C:\Program Files\MySQL\MySQL Server 5.1\bin> .. so this is maybe rather a graceful exit as expected (on CTRL+C). But if console window used by client also closes it 'looks like' a crash.
[18 Nov 2010 18:47]
Michael Clark
No crash for me on WinXP with 5.1.52. One difference is that I am using SSH for Linux testing. Possibly a 64 bit only issue, since both linux boxes are x86_64 (one is a VPS which may cause more oddity - the ArchLinux box is a dedicated PC), and the other person who seems to be able to reproduce is on Win7/64. Console log (no crash): C:\Documents and Settings\michaelc>mysql --version mysql Ver 14.14 Distrib 5.1.52, for Win32 (ia32) C:\Documents and Settings\michaelc>mysql -u root -p Enter password: ************** Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 3 Server version: 5.1.52-community MySQL Community Server (GPL) Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved. This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL v2 license Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> Ctrl-C -- exit! Bye
[18 Nov 2010 18:56]
Sveta Smirnova
Thank you for the feedback. Please try with current version 5.1.52: as nobody could repeat this can be fixed already. If problem still exists please send accurate name of the package you use (file name you downloaded from http://dev.mysql.com/downloads) and output of echo $MALLOC_CHECK_
[19 Dec 2010 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[11 Jan 2011 5:02]
Michael Clark
Package url: http://ftp.gwdg.de/pub/misc/mysql/Downloads/MySQL-5.1/mysql-5.1.54.tar.gz echo $MALLOC_CHECK_: $ echo $MALLOC_CHECK_ $ Version: $ mysql --version mysql Ver 14.14 Distrib 5.1.54, for unknown-linux-gnu (x86_64) using readline 6.1 PKGBUILD (parameters to ./configure, etc): http://projects.archlinux.org/svntogit/packages.git/tree/mysql/repos/extra-x86_64/PKGBUILD The most recent time I noticed my xterm display the message "Output has been suspended by pressing Ctrl-S. Press Ctrl-Q to resume. Relevantly, pressing ctrl-q removes the problem. My sense is that output being suspended is the problem; possibly a bug in readline instead of mysql. I was able to replicate it with 9to my knowledge) the most recent stable version of MySQL.
[11 Jan 2011 5:02]
Michael Clark
Package url: http://ftp.gwdg.de/pub/misc/mysql/Downloads/MySQL-5.1/mysql-5.1.54.tar.gz echo $MALLOC_CHECK_: $ echo $MALLOC_CHECK_ $ Version: $ mysql --version mysql Ver 14.14 Distrib 5.1.54, for unknown-linux-gnu (x86_64) using readline 6.1 PKGBUILD (parameters to ./configure, etc): http://projects.archlinux.org/svntogit/packages.git/tree/mysql/repos/extra-x86_64/PKGBUILD The most recent time I noticed my xterm display the message "Output has been suspended by pressing Ctrl-S. Press Ctrl-Q to resume. Relevantly, pressing ctrl-q removes the problem. My sense is that output being suspended is the problem; possibly a bug in readline instead of mysql. I was able to replicate it with MySQL 5.1.54, therefore it is not fixed.
[8 Jul 2011 18:09]
Sveta Smirnova
Thank you for the feedback. You wrote you use 5.1 client, but provided options for 5.5 build. Which actual build options do you use?
[8 Aug 2011 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[9 Sep 2011 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[1 Apr 2013 21:43]
Michael Clark
Sveta Smirnova, as I am downloading a binary executable, I am not personally using any build options. As Arch Linux has switched to MariaDB for future MySQL upgrades, it will possibly become more difficult to use MySQL for you. How would you like me to find what build options MySQL was compiled with?
[1 Apr 2013 21:54]
Michael Clark
Was able to reproduce in Arch Linux (not updated to MariaDB yet) with version 5.5.30. Since this is the current version used in the buildfile I linked earlier, this should give you correct buildflags. Output of mysql --version: mysql Ver 14.14 Distrib 5.5.30, for Linux (x86_64) using readline 5.1 Was not able to reproduce on current dev vm with MySQL 5.1.56 in Gentoo. Output of mysql --version: mysql Ver 14.14 Distrib 5.1.56, for pc-linux-gnu (x86_64) using readline 5.1
[15 Apr 2013 16:41]
Sveta Smirnova
Michael, thank you for the update. Earlier you wrote: > Package url: > http://ftp.gwdg.de/pub/misc/mysql/Downloads/MySQL-5.1/mysql-5.1.54.tar.gz This is source package, not binary one > PKGBUILD (parameters to ./configure, etc): > http://projects.archlinux.org/svntogit/packages.git/tree/mysql/repos/extra-x86_64/PKGBUILD These are options, used to build version 5.5. Please specify which options you use to build version 5.1.54 or which binary package do you download now.
[16 May 2013 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".