Rick McGuire wrote: > Have you tried building a a debug vsrsion of ooRexx to run with? If > you're running from an installed version, build the debug version and > drop the new .exes and dlls in the install location, along with the > .pdb files containing the debug symbols. > Yes, I always build both packages and install the debug version of ooRexx.
Problem is, that in this use case java.exe takes over (invocation "java Test", where Test.java will invoke twice a Rexx script in different threads, where the Rexx script calls another Rexx script) and the debugger never gets to step in, instead the hs*.log file is created giving those hexadeciaml offsets (?) in the respective dll's, including rexx.dll and BSF4Rexx.dll. Hence, if I could figure out from that information which statement in the respective dll this refers to, it would help me locate the area such that further debugging at that spot became possible. Am trying to set breakpoints in the BSF4Rexx.dll upfront in order to get the debugger to step in, but to no avail so far (am practically a rookie in using the MSVS debugger in this context :( ). ---rony ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
