| Author |
 Topic  |
|
|
srmcarneir
Brazil
33 Posts |
 Posted - 06/01/2004 : 4:36:27 PM
|
Hi All,
I am using OriginPro 7.0, SR4, under Win2k.
A LabTalk script that calls OriginC routines.
Sometimes we can see error messages that lead to the application termination. A message box pops up to tell that the memory could not be read due to certain position being referenced by another position.
By applying Cancel we have another message box saying that an error log is being created then the application terminates. Should we look for that under a log file? Where is that saved? Guess it would be a useful debug tool.
Besides, is there any approach we could seek when calling OriginC routines from LabTalk scripts? Do you have any known case of dangerous techniques on this issue?
Regards,
Ricardo Carneiro |
|
|
easwar
USA
1965 Posts |
Posted - 06/01/2004 : 5:46:01 PM
|
Hi Ricardo,
Currently there is no log file - the memory locations shown in the dialog can help often if included in your report to tech support etc.
But, before going that route, I suggest the following:
1> Open your OC file that contains the function which gets called from LabTalk
2> Place a break point in the function body
3> Run your LT script and debug into the OC function
4> Step over each statement, and see where it crashes.
This could shed some light into what may be causing the crash. Once you narrow down to some OC statement(s) then maybe you can post those statements and/or your entire OC function here? Or send that info directly to tech support?
Easwar
OriginLab
Edited by - easwar on 06/01/2004 5:46:37 PM |
 |
|
|
srmcarneir
Brazil
33 Posts |
Posted - 06/02/2004 : 12:02:58 PM
|
Thanks Easwar, All,
No clue I could get. But I suspect that swapping the plotting command "layer -i %f_%S;" by "graph %f_%S;"
in the LabTalk code could have made the difference.
It miraculously stopped crashing (after that?).
In fact I had already followed the rules you mentioned in your message before posting my first topic; it seemed to crash randomly, not at a specific point of the code.
Something that I would like to understand is how to trace the memory position mentioned in the message box. Every time this particular
error of mine occurred the memory position was the same 0x062540f2
referred to somewhere else...
Anyway, I am glad the code seems to be stable again.
And thanks to all who helped by thinking of a solution to this case.
Regards,
Ricardo Carneiro |
|
|
| |
Topic |
|
|
|
Creation of an error log