Reported by michelpons, 15 years ago.

De: Michel Pons [technologyofficer@…] Envoyé: Wednesday, June 24, 2009 10:50 PM À: 'Ahsan Akhtar' Cc: 'Michael Halloran' Objet: COLTT 09-014 Debug and crash for GLCC in PRO/II

Pièces jointes: proii_062409_223724.log

Ahsan,

I have a scenario showing a strange behaviour on COLTT 1.08.02. It involves a UO PMC (GLCC) and PRO/II 8.3. Without COLTT enabled on GLCC UO, the calculation of the UO does not go well and I wanted to look at the log in order to figure out what was going on.

However enabling COLTT 1.08.02 on GLCC leads first to a debug assertion error then a crash a bit after instantiating the GLCC UO within the PRO/II flowsheet.

In fact I have two crash messages as follows:

Microsoft Visual C++ Debug Library

Debug Assertion Failed!

Program: C:
SIMSCI
PROII83
Bin
PROII.EXE

File: d:
program files
microsoft visual studio 9.0
vc
atlmfc
include
atlcomcli.h

Line: 154

Expression: p!=0

For information on how your program can cause an assertion

failure, see the Visual C++ documentation on asserts.

(Press Retry to debug the application)

Abandonner Recommencer Ignorer

I selected « Ignore » and got :

Exception Detected

Exception code 0xc0000005: EXCEPTION_ACCESS_VIOLATION

The thread tried to read from or write to a virtual address for which it does not have the appropriate access.

Select Cancel to debug or OK to save the copy and quit.

OK Annuler

Exception Detected

Exception code 0xc0000005: EXCEPTION_ACCESS_VIOLATION

The thread tried to read from or write to a virtual address for which it does not have the appropriate access.

Select Cancel to debug or OK to save the copy and quit.

OK Annuler

There is a short log created. It is attached. I have numbered this issue 09-014. Let me know if you need Visual Studio 2008 installed in the VM dedicated to this issue.

Best regards

Michel

Reported by michelpons, 14 years ago.

De: Michel Pons [technologyofficer@…] Envoyé: Thursday, June 18, 2009 11:11 AM À: 'Ahsan Akhtar' Cc: 'michaeljhalloran@…' Objet: SimSci UO in PRO/II

Pièces jointes: MyScreenCopies.doc

Hi,

In the attached Word document I have documented a scenario that leads to a crash in PRO/II when either COLTT 1.07 or 1.08.02 is enabled on a UO. I think that the crash is related to the fact that the UO is 0.93 compliant. Could there be a way to avoid such a crash which does not look good?

I have listed this issue as 09-012.

Best regards

Michel

Reported by michelpons, 14 years ago.

I am using the GLCC UO in PRO/II 8.3 Patch 1. It relates to a case raised with SimSci-Esscor Support. I have a scenario that calls fro dropping the GLCC UO on the PRO/II flowsheet, to connect inlet and outlet ports, to edit the UO in order to choose the location for its output file, then to calculate the process model made of this UO. Examining the log made with COLTT, I see that get_Values calls on the integer parameters of the UO are at first looking good. Then, after the Edit call, the get_Values calls for integer parameters return a message \"An Invalid Argument\". What is not clear is who is sending this message and then what it means exactly. The only argument of such a call is the returned value. There is no error raised and no means for the call to pass a message. So my educated guess is that COLTT is posting the message but on what grounds. Plus, if it is indeed COLTT which is posting the message, it should be made obvious. Here, as it is posted, one may think that get_Value returns this message. Would it be possible to get more info on what is going on?