On 14.02.2017 20:56, Erich Steinböck wrote:
> | If you have ideas what to look for in Visual Studio once I am able to get
> the debugging working,
> I would appreciate it
> As Rick wrote: examine the thread/call stack
>
> If this is another case of an object getting garbage-collected before being
Well, as expected this will take a while until getting acquainted with the
Visual Studio debugger.
One way to start it was using Rick's command line arguments.
The other possibility was to have the Rexx script paused (parse pull) before it
reached the area
where the exception would occur. Then
| If you have ideas what to look for in Visual Studio once I am able to get
the debugging working, I would appreciate it
As Rick wrote: examine the thread/call stack
If this is another case of an object getting garbage-collected before being
protected, you'll find a call stack example and some com
On 13.02.2017 21:28, Erich Steinböck wrote:
> Rony, I've built a 5.0 32-bit Debug installer and uploaded it to our files
> section as
> oorexx/5.0.0beta/ooRexx.5.0.0.0-x86_32-debug.exe
Thank you *very* much for the debug build!
Still trying to set up the environment to have both functional, Rexx
