[Oorexx-bugs] [ oorexx-Bugs-2822848 ] Unknown file path reported in stack overflow

[SourceForge.net <no...@so...>]

Bugs item #2822848, was opened at 2009-07-16 18:57
Message generated for change (Comment added) made by miesfeld
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2822848&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Interpreter
Group: v4.0beta
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mark Gaubatz (mgaubatz)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unknown file path reported in stack overflow

Initial Comment:
4.0 RC 2; Ubuntu 9.04

Directory /home/miesfeld/work.ooRexx/wc/ooRexx-4.0.0 as reported by the error message does not exist on this machine.

REX0011E: Error 11 running /home/miesfeld/work.ooRexx/wc/ooRexx-4.0.0/CoreClasses.orx line 976:  Control stack full
REX0218E: Error 11.1:  Insufficient control stack space; cannot continue execution



----------------------------------------------------------------------

>Comment By: Mark Miesfeld (miesfeld)
Date: 2009-07-16 20:33

Message:
In and of itself the file path is not a bug.  It is a product of where the
interpreter is built.  The path name is embedded in rexx.img when it is
built.

For instance if I take the rexx.img on the machine I'm currently using I
can find this string embedded:

C:\work.ooRexx\wc\main\Win32Dbg\CoreClasses.orx

The Rexx code in CoreClasses.orx looks like:

::METHOD unknown unguarded

/**************************************************************************/
 /* Class  Monitor                                                        
*/
 /* Method UNKNOWN                                                        
*/
 /* Function                                                              
*/
 /*        To forward any message sends that are not monitor messages     
*/
 /*        to the currently active destination                            
*/
 /* Input  Message name and Argument list                                 
*/
 /* Output Any return from the forwarded message                          
*/

/**************************************************************************/
 /* unknown: forward monitored message to destination */
  expose destination
  use strict arg msgname, arglist

  forward to (destination~peek) message (msgname) arguments (arglist)

The 'forward to' line is line 976.

It might be interesting to find out why the error is being raised at that
point, but the fact that the path name does not exist on your system is not
significant.  It is to be expected.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2822848&group_id=119701