MySQL Bugs: #39421: Uncaught exception EOF in Falcon recovery on Windows

Bug #39421	Uncaught exception EOF in Falcon recovery on Windows
Submitted:	12 Sep 2008 16:14	Modified:	8 Jan 18:20
Reporter:	Philip Stoev
Status:	Closed
Category:	Server: Falcon	Severity:	S2 (Serious)
Version:	6.0-falcon-team	OS:	Microsoft Windows
Assigned to:	Vladislav Vaintroub	Target Version:	6.0.8
Triage:	Triaged: D2 (Serious)

Description:
When Falcon does recovery on Windows, it always reports an exception when it reaches the
end of the serial log. According to Ann, this is harmless, however the testing tools can
not distinguish between a harmless exception and a one that destroys the entire database.
So, understandably, all exceptions are reported as failures.

How to repeat:
See pushbuild2, code.

Suggested fix:
* Any and all harmless exceptions must be caught. An uncaught exception means recovery
failure.

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/commits/53991

2819 Vladislav Vaintroub	2008-09-12
      Bug#39421 - messages during recovery about exceptions from ReadFile.
      Fix:
      Ignore ERROR_HANDLE_EOF coming from ReadFile(). Read should just return 0 
      like it does in Posix case.

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/commits/53996

2819 Vladislav Vaintroub	2008-09-12
      Bug#39421 - messages during recovery about exceptions from ReadFile.
      Fix:
      Ignore ERROR_HANDLE_EOF coming from ReadFile(). Read should just return 0 
      like it does in Posix case.

A note has been added to the 6.0.8 changelog: 

When performing a recovery of a crashed Falcon table on Windows, MySQL would report an
exception when then recovery process completed, even though the recovery may have
completed successfully