View previous topic :: View next topic |
Author |
Message |
wahorger
Joined: 13 Oct 2014 Posts: 1227 Location: Morrison, CO, USA
|
Posted: Fri Mar 01, 2024 3:12 pm Post subject: Forcing a traceback |
|
|
RE: SCC /64 routines: Is there a method by which an error can be communicated that then will result in a callback trace being performed?
The 64-bit compilation of this code (coordinate transforms) does not operate like the 32-bit. It might be that it was not written in a "safe" manner (re: pointers) and is not working. I need to identify the path withing the code to see what is perhaps not coded correctly, and having a method by which the traceback can be performed would be helpful. |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8037 Location: Salford, UK
|
Posted: Fri Mar 01, 2024 4:38 pm Post subject: |
|
|
If you insert the following line of code then a break point will be generated at that point...
|
|
Back to top |
|
|
wahorger
Joined: 13 Oct 2014 Posts: 1227 Location: Morrison, CO, USA
|
Posted: Fri Mar 01, 2024 6:24 pm Post subject: |
|
|
Awesome!! |
|
Back to top |
|
|
wahorger
Joined: 13 Oct 2014 Posts: 1227 Location: Morrison, CO, USA
|
Posted: Fri Mar 01, 2024 7:06 pm Post subject: |
|
|
When I compile, I get:
Code: | 0089 asm {int 3; }
*** Error 79: 'asm' has not been declared
1 ERRORS [<PJ_PARAM> SCC/WIN32 Ver 4.61]
|
|
|
Back to top |
|
|
wahorger
Joined: 13 Oct 2014 Posts: 1227 Location: Morrison, CO, USA
|
Posted: Fri Mar 01, 2024 7:56 pm Post subject: |
|
|
Discovered the problem. I am using /ANSI_C as an option and it does not like this construct! |
|
Back to top |
|
|
|