Bug #18987 | Crashes during test "connect" | ||
---|---|---|---|
Submitted: | 10 Apr 2006 20:12 | Modified: | 4 Oct 2006 17:55 |
Reporter: | Joerg Bruehe | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0.20 + 5.1.10 | OS: | different Unix |
Assigned to: | Magnus BlÄudd | CPU Architecture: | Any |
[10 Apr 2006 20:12]
Joerg Bruehe
[10 May 2006 12:23]
Joerg Bruehe
First such effect occurred in 5.0.19 and 5.1.9-beta (according to the test isolation, may be incomplete), in 5.0.20 and 5.1.10-beta it increased.
[28 May 2006 21:55]
Jani Tolonen
Tested with latest 5.0 and 5.1, cannot repeat the problem. Tests pass. Using latest bk source, 5.0.23 and 5.1.12-beta. Platform: SuSE 10.0, i686 gcc: 4.0.2 (standard SuSE package) If someone can repeatedly repeat this problem, please turn on the debug with mysql-test-run. mysql-test-run --debug. Please include also information on the platform used. Please attach also information about the build; was it compiled from source or a binary? Once started with --debug, please check the trace file after a broken test. It should be compared with a trace file of the same test on a platform where it passes. Source must the same for both.
[8 Jun 2006 12:25]
Joerg Bruehe
I confirm Jani's last result: In test builds, both 5.0.23 and 5.1.12 pass this test on all platforms. It seems some in-between change fixed this as a by-product.
[18 Sep 2006 9:18]
Joerg Bruehe
Sorry about bad news: The bug re-occurred in the release build for 5.0.25, In the "prepared statement" run of a "standard" build on SCO. I will try to repeat it, using the "debug" test run as asked by Jani (above).