Bug #14103 IM tests fail on SCO
Submitted: 18 Oct 2005 1:07 Modified: 28 Oct 2005 11:01
Reporter: Petr Chardin Email Updates:
Status: Closed Impact on me:
None 
Category:Instance Manager Severity:S3 (Non-critical)
Version: OS:Other (SCO)
Assigned to: Petr Chardin CPU Architecture:Any

[18 Oct 2005 1:07] Petr Chardin 
Description:
IM im_options_set and  im_options_unset tests are failing on SCO:

mysqldev@opnsrv6c:~/petr/mysqlcom-5.0.15/mysql-test> ./mysql-test-run.pl im_options_set
<cut>

TEST                           RESULT
-------------------------------------------------------

im_options_set                 [ fail ]

Errors are (from /home/mysqldev/petr/mysqlcom-5.0.15/mysql-test/var/log/mysqltest-time) :
mysqltest: At line 121: query 'FLUSH INSTANCES' failed: 2013: Lost connection to MySQL server during query
(the last lines may be the most important ones)

How to repeat:
run tests on SCO

Suggested fix:
SCO's default stack size is too small, which results in a crash when option processing functions are called in some cases. E.g. when the stack is already full with various stuff.
The crash occurs in search_default_file_with_ext, where we use unneccessary large piece
of the stack for local arrays (4k*3). We should rather use 1k buffers.
[18 Oct 2005 1:11] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/31202
[28 Oct 2005 9:36] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/31603
[28 Oct 2005 10:38] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/31606
[28 Oct 2005 11:01] Petr Chardin 
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

Additional info:

pushed into 5.0.16