Bug #1589
during parsing the .lexer file is sometimes arbitrarily truncated
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
10/12/2012
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
History
#1 Updated by Greg Shah over 11 years ago
This behavior can be seen by:
1. Make an exact copy of a conversion project (duplicate the entire directory tree).
2. Run conversion in the original.
3. Run conversion in the copy.
4. Compare all .lexer files. Note the differences.
5. If the problem doesn't present itself, rerun conversion in the copy and examine again.
The problem was originally seen in #1565. Look there for more specific examples.
The problem may be dependent upon a large conversion project. Just a guess, but it seems that the cause may be somehow related to not flushing output before closing a stream.