0025275: Different result of reading operation from *.igs and *.stp file for WINDOWS and LINUX platforms

View Revisions: Issue #25275		[ All Revisions ] [ Back to Issue ]
Summary	0025275: Different result of reading operation from .igs and .stp file for WINDOWS and LINUX platforms

Revision	2014-12-12 16:31 by nbv
Description	For example, there is the file UKI60107-6.igs in OCCT Base with following structure. Useful data are in line-range from 1 to 11092 (see file_content.png attached picture). Next lines contain not actual data. [In the picture file is showed with unprinted symbols, such as LF (ASCII-code 0x0A), SUB (ASCII-code 0x1A), BEL (ASCII-code 0x07) etc.] WINDOWS reads only (!) these 1092 lines, after that it breaks to read in reason of meeting end of file. LINUX continues reading. It results in this error: "1 F: Syntax error in IGES file at line 11093 in section T." (see test de iges_3 A3 in DEBUG mode on LINUX platform). On WINDOWS platform these errors are absent.

Revision	2014-12-09 13:35 by nbv
Description	For example, there is the file UKI60107-6.igs in OCCT Base with following structure. Useful data are in line-range from 1 to 11092 (see file_content.png attached picture). Next lines contain not actual data. [In the picture file is showed with unprinted symbols, such as LF (ASCII-code 0x0A), SUB (ASCII-code 0x1A), BEL (ASCII-code 0x07) etc.] WINDOWS reads only (!) these 1092 lines, after that it breaks to read in reason of meeting end of file. LINUX continues reading. It results in this error: "1 F: Syntax error in IGES file at line 11093 in section T." (see test de iges_3 A3 in DEBUG mode on LINUX platform). On WINDOWS platform these errors are absent. Additionally, it is important for IGES and STEP file format to add check, if if wrong data are read from the file. For example, if file contains number ~ 1.0e-314 (less than DBL_MIN) or Nan-numbers (see wrongnum.PNG file attached).

Revision	2014-12-09 13:34 by nbv
Description	For example, there is the file UKI60107-6.igs in OCCT Base with following structure. Useful data are in line-range from 1 to 11092 (see file_content.png attached picture). Next lines contain not actual data. [In the picture file is showed with unprinted symbols, such as LF (ASCII-code 0x0A), SUB (ASCII-code 0x1A), BEL (ASCII-code 0x07) etc.] WINDOWS reads only (!) these 1092 lines, after that it breaks to read in reason of meeting end of file. LINUX continues reading. It results in this error: "1 F: Syntax error in IGES file at line 11093 in section T." (see test de iges_3 A3 in DEBUG mode on LINUX platform). On WINDOWS platform these errors are absent. Additionally, it is important for IGES and STEP file format to add check, if if wrong data are read from the file. For example, if file contains number ~ 1.0e-314 (less than DBL_MIN) or Nan-numbers.

Revision	2014-12-09 13:33 by nbv
Description	For example, there is the file UKI60107-6.igs in OCCT Base with following structure. Useful data are in line-range from 1 to 11092 (see file_content.png attached picture). Next lines contain not actual data. [In the picture file is showed with unprinted symbols, such as LF (ASCII-code 0x0A), SUB (ASCII-code 0x1A), BEL (ASCII-code 0x07) etc.] WINDOWS reads only (!) these 1092 lines, after that it breaks to read in reason of meeting end of file. LINUX continues reading. It results in this error: "1 F: Syntax error in IGES file at line 11093 in section T." (see test de iges_3 A3 in DEBUG mode on LINUX platform). On WINDOWS platform these errors are absent. Additionally, it is important for IGES and STEP file format to add check, if if wrong data are read from the file. For example, if file contains number ~1.0e-314 (less than DBL_MIN) or Nan-numbers.

Revision	2014-09-26 09:53 by nbv
Description	For example, there is the file UKI60107-6.igs in OCCT Base with following structure. Useful data are in line-range from 1 to 11092 (see file_content.png attached picture). Next lines contain not actual data. [In the picture file is showed with unprinted symbols, such as LF (ASCII-code 0x0A), SUB (ASCII-code 0x1A), BEL (ASCII-code 0x07) etc.] WINDOWS reads only (!) these 1092 lines, after that it breaks to read in reason of meeting end of file. LINUX continues reading. It results in this error: "1 F: Syntax error in IGES file at line 11093 in section T." (see test de iges_3 A3 in DEBUG mode on LINUX platform). On WINDOWS platform these errors are absent.