Thanks. Will have to create a local setup of what they are doing, in
order to become able to debug locally.
---rony
P.S.: They also report the same error if increasing the Java thread
stack size from 256KB to 512KB.
At setting it to 1MB the following error occurs:
Error 11 running /usr/bin/UNO.CLS line 1154: Control stack full
Error 11.1: Insufficient control stack space; cannot continue execution
Again, will have to look into it locally (seems to be a little bit odd
that having such a huge stack will eventually yield a "Control stack
full" error).
On 12.02.2011 14:51, Rick McGuire wrote:
> I see nothing in this stack trace to indicate that this problem is
> occurring on Rexx code. The items at the point of the crash are all
> in the BSFRexx routines.
>
> Rick
>
> On Sat, Feb 12, 2011 at 3:07 AM, Rony G. Flatscher
> <rony.flatsc...@wu-wien.ac.at> wrote:
>
>> With setting "-Xss" the control stack error could be overcome, however
>> another error occurs, for which the Java debug information with the
>> stack trace is given enclosed.
>>
>> It seems that the problem occurs within Rexx. If so, is there anything I
>> could do, go after to debug the cause?
>>
>> ---rony
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
