Bug #4569 Current 4.1 tree fails in the ps_2myisam
Submitted: 15 Jul 2004 21:49 Modified: 30 Jul 2004 16:43
Reporter: Lenz Grimmer Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: MyISAM storage engine Severity:S2 (Serious)
Version:4.1 OS:
Assigned to: CPU Architecture:Any

[15 Jul 2004 21:49] Lenz Grimmer
below please see an example of the test failure - I noticed it on several
platforms, e.g. Mac OS X 10.3, AIX 5.2, Linux/PPC and Linux/AXP.
var/log/master.err on Linux/AXP (ds20) revealed the following:

CURRENT_TEST: ps_2myisam
mysqld: item.cc:921: Assertion `0' failed.
mysqld got signal 6;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly
built, or misconfigured. This error can also be caused by malfunctioning
hardware. We will try our best to scrape up some info that will hopefully
help diagnose the problem, but since we have already crashed, something is
definitely wrong and this may fail.
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 39423 bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Writing a core file

Unfortunately there was no core file :(

It also does not seem to finish when I enable the --debug option to create
a trace file, these are the last lines in the trace before it stops:

T@9226 : | | <mysql_execute_command
T@9226 : | | >query_cache_end_of_result
T@9226 : | | <query_cache_end_of_result
T@9226 : | | >Item::cleanup

ps_1general                    [ pass ]
ps_2myisam                     [ fail ]

Errors are (from /home/mysqldev/pegasos1/test/mysql-debug-4.1.4-beta-unknown-linux-powerpc/mysql-test/var/log/mysqltest-time) :
/home/mysqldev/pegasos1/test/mysql-debug-4.1.4-beta-unknown-linux-powerpc/bin/mysqltest: At line 241: query 'execute stmt1 using @arg00'
failed: 1054: Unknown column '?' in 'order clause'
(the last lines may be the most important ones)

Aborting: ps_2myisam failed. To continue, re-run with '--force'.

I hope that helps to investigate this!

How to repeat:
Run the test suite on one of the platforms mentioned above
[30 Jul 2004 16:43] Sergei Golubchik
I assume it's fixed ?