Bug #927 test_stc example crashes with --skip-innodb option and output redirect
Submitted: 25 Jul 2003 7:05 Modified: 29 Jul 2003 9:23
Reporter: dmitriy burashnikov Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Embedded Library ( libmysqld ) Severity:S3 (Non-critical)
Version:4.0.14a OS:Windows (Windows XP SP1)
Assigned to: CPU Architecture:Any

[25 Jul 2003 7:05] dmitriy burashnikov
Description:
test_stc.dsp that comes in mysq/Embedded/Static/release compiles without any warning. It works fine just until you supply --skip-innodb option with output redirect.
Example: 
test_stc.exe --skip-innodb | more
In 50% cases return folowing error dialog:
--
test_stc.exe - Application Error
The instruction at "0x7769ecd" referenced memory at "0x00000010". The memory could not be "written".
--

This fails only when stdout is redirected into file, or into other program like more...

How to repeat:
Compile test_stc.exe
Run: test_stc.exe --skip-innodb | more
It will report Application Error with failure rate about 50%

Suggested fix:
You suggest ;))
[25 Jul 2003 9:15] dmitriy burashnikov
Actually, I noticed that commenting out call to mysql_server_end() function solves the issue
[29 Jul 2003 9:23] MySQL Verification Team
C:\mysql\Embedded\Static\release>test_stc.exe --skip-innodb | more

>> mysql
>> test