Bug #1836 mysql client crashes on exit (segmentation fault)

• Submitted: 14 Nov 2003 7:07
• Modified: 15 Nov 2003 1:14
• Reporter: already told you already told you
• Status: Closed
• Category: MySQL Server: Command-line Clients
• Severity: S2 (Serious)
• Version: 4.1.0-alpha
• OS: Linux (redhat 7.3 x86)
• CPU Architecture: Any

[14 Nov 2003 7:07] already told you already told you

Description:
mysql client works fine but crashes on exit (segmentation fault); 
- no changes applied to system, RPMs, mysqld
- used to work fine for months.
- crashes happen after writing and running an heavy consolidation SQL batch (1 main table is full scanned many times ; couples of temporary are created + dropped)

tried then to :
 - FLUSH QUERY CACHE : no changes
 - FLUSH LOGS : no changes
 - FLUSH TABLES : no changes
 - stop/restart mysqld : no changes

How to repeat:
Linux RH 7.3  2.4.20-18.7MySQL-devel-4.1.0-0
MySQL-devel-4.1.0-0
php-mysql-4.1.2-7
MySQL-client-4.1.0-0
libmysql10-3.23.47-5.2mdk
MySQL-server-4.1.0-0

 works fine, build a complex batch involving 6 tables (1 "big" = 1000000 records, 5 "tiny"), then test it, and here comes the 'segmentation fault' ..

[15 Nov 2003 1:14] Alexander Keremidarski

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
    http://www.mysql.com/doc/en/Installing_source_tree.html

This problem does not exists anymore in current 4.1 source which will be soon released as 4.1.1

Side note:

If you want to have 3.23 client libraries you can install MySQL-shared-compat RPM