Rony,
for ooRexx 5.0 you create a Debug-Version by adding
-DCMAKE_BUILD_TYPE=DEBUG (or -DCMAKE_BUILD_TYPE=RELWITHDEBINFO) to the
build step (I've added a brief description of how to build ooRexx to
our sourceforge
Wiki <https://sourceforge.net/p/oorexx/wiki/Home/>)
I'd be willing to provide a Debug-Version for 5.0 if requested.
On Windows the debugger (Visual Studio Just-In-time Debugger) is
automatically installed with MSVC and will show up as an option when
rexx.exe crashed (Close the program, Debug the program). As the crash is
often "too late", you'd have to follow Rick's advice, starting rexx
directly with the debugger.
Personally I find it very difficult to master the debugger. We have quite
a lot of open bugs, that I can't fix, simply because I'm unable to debug
them to find the root cause.
For most issues I will just sprinkle the code with a few printf's to see
what's going on and then read the source code to see what needs to get
fixed.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
