Archived issue #0027313
Exception during WriteStep with PMI
Description
Version windows Release opencascade-7.0.0-vc10-64-rc
1. Start draw.bat
2. Execute attached script (source Attachment 1 (TCL))
3. Enter in command line
XAddDatum D v2_6; #0:1:4:5
XSetDatumName D 0:1:4:5 A;
XAddDatumModifier D 0:1:4:3 14;
XSetDatum D 0:1:4:5 0:1:4:4
WriteStep D wing1.stp
Bug: file is not saved
An exception was caught 0000000002115080 : OSD_Exception_ACCESS_VIOLATION: ACCESS VIOLATION at address 0x00000020 during 'READ' operation
** Exception ** 0000000002115080 : OSD_Exception_ACCESS_VIOLATION: ACCESS VIOLATION at address 0x00000020 during 'READ' operation
1. Start draw.bat
2. Execute attached script (source Attachment 1 (TCL))
3. Enter in command line
XAddDatum D v2_6; #0:1:4:5
XSetDatumName D 0:1:4:5 A;
XAddDatumModifier D 0:1:4:3 14;
XSetDatum D 0:1:4:5 0:1:4:4
WriteStep D wing1.stp
Bug: file is not saved
An exception was caught 0000000002115080 : OSD_Exception_ACCESS_VIOLATION: ACCESS VIOLATION at address 0x00000020 during 'READ' operation
** Exception ** 0000000002115080 : OSD_Exception_ACCESS_VIOLATION: ACCESS VIOLATION at address 0x00000020 during 'READ' operation
Steps to reproduce
Dear GKA,
could you please review branch CR27313?
could you please review branch CR27313?
Public activity
9 archived notes
Participants are labeled by their role within this record.
Branch [archived branch] has been created by Commenter 4.
[revision removed]
Detailed log of new commits:
Author: Commenter 4
Date: Tue Jun 28 12:00:13 2016 +0300
0027313: Exception during WriteStep with PMI
Add check for datum position during export of datum_system
Add Draw commands for set/get datum position
update test cases
[revision removed]
Detailed log of new commits:
Author: Commenter 4
Date: Tue Jun 28 12:00:13 2016 +0300
0027313: Exception during WriteStep with PMI
Add check for datum position during export of datum_system
Add Draw commands for set/get datum position
update test cases
Branch [archived branch] has been updated forcibly by Commenter 4.
[revision removed]
[revision removed]
Dear GZY,
the first problem was in STEP Application Protocol:
use "param write.step.schema 5" to export PMI correctly to STEP AP242.
The second problem was in absence of "datum position" this number should be in {1, 2, 3}, it is used to find a correct position of datum in geometric tolerance datum system (for example, |value|A|B| or |value|B|A| or |value|A-B|, where A and B are datums, will be different geometric tolerances).
A new command XSetDatumPosition was added, please use it to specify datum position number.
Also in XSetDatum command was added a reject message, if datum position is not specified.
the first problem was in STEP Application Protocol:
use "param write.step.schema 5" to export PMI correctly to STEP AP242.
The second problem was in absence of "datum position" this number should be in {1, 2, 3}, it is used to find a correct position of datum in geometric tolerance datum system (for example, |value|A|B| or |value|B|A| or |value|A-B|, where A and B are datums, will be different geometric tolerances).
A new command XSetDatumPosition was added, please use it to specify datum position number.
Also in XSetDatum command was added a reject message, if datum position is not specified.
Branch CR27313 is ready to be tested.
Branch [archived branch] has been updated forcibly by Participant.
[revision removed]
[revision removed]
Branch [archived branch] has been rebased on the current master.
Branch [archived branch] has been updated by Participant.
[revision removed]
Detailed log of new commits:
Author: apv
Date: Mon Sep 12 09:55:18 2016 +0300
Correction of case bugs/step/bug27313
[revision removed]
Detailed log of new commits:
Author: apv
Date: Mon Sep 12 09:55:18 2016 +0300
Correction of case bugs/step/bug27313
Dear Commenter 1,
Branch CR27313 from occt git-repository (and master from products git-repository) was compiled on Linux, MacOS and Windows platforms and tested.
[revision removed]
Number of compiler warnings:
occt component:
Linux: 0 (0 on master)
Windows: 0 (0 on master)
MasOS: 0 (0 on master)
products component:
Linux: 64
Windows: 0
MacOS: 1128
Regressions/Differences:
Not detected
Testing cases:
bugs step bug27313 - OK
http://occt-tests/CR27313-master-OCCT/Debian70-64/bugs/step/bug27313.html
http://occt-tests/CR27313-master-OCCT/Windows-64-VC10/bugs/step/bug27313.html
Testing on Linux:
Total MEMORY difference: 90258086 / 90377803 [-0.13%]
Total CPU difference: 19403.83 / 19445.410000000134 [-0.21%]
Testing on Windows:
Total MEMORY difference: 57155001 / 57172575 [-0.03%]
Total CPU difference: 18233.64648159888 / 18100.047225198865 [+0.74%]
Branch CR27313 from occt git-repository (and master from products git-repository) was compiled on Linux, MacOS and Windows platforms and tested.
[revision removed]
Number of compiler warnings:
occt component:
Linux: 0 (0 on master)
Windows: 0 (0 on master)
MasOS: 0 (0 on master)
products component:
Linux: 64
Windows: 0
MacOS: 1128
Regressions/Differences:
Not detected
Testing cases:
bugs step bug27313 - OK
http://occt-tests/CR27313-master-OCCT/Debian70-64/bugs/step/bug27313.html
http://occt-tests/CR27313-master-OCCT/Windows-64-VC10/bugs/step/bug27313.html
Testing on Linux:
Total MEMORY difference: 90258086 / 90377803 [-0.13%]
Total CPU difference: 19403.83 / 19445.410000000134 [-0.21%]
Testing on Windows:
Total MEMORY difference: 57155001 / 57172575 [-0.03%]
Total CPU difference: 18233.64648159888 / 18100.047225198865 [+0.74%]
Branch [archived branch] has been deleted by Commenter 5.
[revision removed]
[revision removed]
Related records