| Bug #12439 | yassl: Infinite loop in "mysqltest" at the end of a test case | ||
|---|---|---|---|
| Submitted: | 8 Aug 2005 16:36 | Modified: | 27 Sep 2005 10:27 |
| Reporter: | Joerg Bruehe | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Command-line Clients | Severity: | S2 (Serious) |
| Version: | 5.0.11 | OS: | Linux (Linux (i686, x86_64, ia64)) |
| Assigned to: | Magnus Blåudd | CPU Architecture: | Any |
[9 Aug 2005 6:27]
Lenz Grimmer
Additional info discovered when running the same test on Red Hat Enterprise Linux 4: [SNIP] ./mysql-test-run --ps-protocol init_connect Installing Test Databases Removing Stale Files [...] Loading Standard Test Databases Starting Tests TEST RESULT ------------------------------------------------------- *** glibc detected *** double free or corruption (!prev): 0x09efb4a0 *** init_connect [ fail ] Errors are (from /home/mysqldev/rpm/BUILD/mysql-5.0.11-beta/mysql-test/var/log/mysqltest-time) : mysqltest returned unexpected code 134, it has probably crashed (the last lines may be the most important ones) Aborting: init_connect failed in ps-protocol mode. To continue, re-run with '--force'. [SNIP] So something in "mysqltest" is fishy...
[9 Aug 2005 18:49]
Joerg Bruehe
See also bug#12457: Rebuilding on "hammer", "ita2", and "quadita2" from same sources, but without "yassl", there is no hang on these machines, and "init_connect" passes. So it seems (at least partially) to be a "yassl" effect.
[26 Aug 2005 13:54]
Magnus Blåudd
Seems to be a duplicate of BUG#12528. Will investigate.
[29 Aug 2005 12:46]
MySQL Verification Team
Verified on Linux Suse 9.3: TEST RESULT ------------------------------------------------------- init_connect [ fail ]
[27 Sep 2005 10:27]
Magnus Blåudd
This problem have been fixed by the latest changes to mysqltest and yassl
Description: Build of 5.0.11, based on ChangeSet 1.1950.1.1 05/08/06 03:10:35 kent@mysql.com +1 -0 make_win_src_distribution.sh: Added missing backslashes At the end of test "init_connect", client "mysqltest" enters an infinite loop and needs to be killed: init_connect [ fail ] Errors are (from PATH/mysqltest-time) : mysqltest returned unexpected code 143, it has probably crashed (the last lines may be the most important ones) Killing the server does not clear the hang. Occurred: build: cluster, debug, max, pro, standard ps-protocol hammer-glibc23: cluster, debug, max, pro, standard normal + ps-protocol quadita2-glibc23-5.0-cluster.log normal quadita2-glibc23: cluster, debug, max, pro, standard ps-protocol Hopefully related: In two cases, the client crashed: init_connect [ fail ] Errors are (from PATH/mysqltest-time) : mysqltest returned unexpected code 139, it has probably crashed (the last lines may be the most important ones) Occurred: ita2-rhas21-5.0-debug.log normal production-icc-glibc23-5.0-standard.log ps-protocol How to repeat: Run the test suite.