Silverfrost Forums

Welcome to our forums

Forcing a traceback

1 Mar 2024 2:12 #31183

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.

1 Mar 2024 3:38 #31191

If you insert the following line of code then a break point will be generated at that point...

  asm { int 3; }
1 Mar 2024 5:24 #31194

Awesome!!

1 Mar 2024 6:06 #31197

When I compile, I get:

   0089 asm {int 3; }
*** Error 79: 'asm' has not been declared
    1 ERRORS  [<PJ_PARAM> SCC/WIN32 Ver 4.61]
1 Mar 2024 6:56 #31198

Discovered the problem. I am using /ANSI_C as an option and it does not like this construct!

Please login to reply.