O.K., this may be a little bit weird: I can manage to have the test code run
without an exception,
repeatedly!
Background: in the native code I have many, many output statements to stderr
for debugging (tons
over the years, controlled by defines) in the form of, e.g:
fprintf(stderr, "...\t\t\t\t\targ(%d)=[%s]\n", idx,
rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING")));
fflush(stderr);
Changing the above output to:
fprintf(stderr, "...\t\t\t\t\targ(%d)=[%*.64*s]\n", idx,
rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING")));
fflush(stderr);
makes the test code run it seems!
Without restricting the output to a maximum of 64 bytes causes variable long
strings, including the
source code of executed Rexx scripts to be displayed. The longest such
displayed string is around
6.6 KB large. It is then that I receive the exceptions as if the
fprintf-statement (or the
formatting of the string to output) overlays some Rexx memory causing
eventually that exception.
Could that be possible?
---rony
------------------------------------------------------------------------------
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
