4.1.0_release_blocker requested: [Issue 124509] MacOSX 64 crash in the scripting environment due to getenv(PATH) returning a null value

2014-03-25 Thread bugzilla
r...@apache.org has asked  for 4.1.0_release_blocker:
Issue 124509: MacOSX 64 crash in the scripting environment due to
getenv(PATH) returning a null value
https://issues.apache.org/ooo/show_bug.cgi?id=124509


--- Additional Comments from r...@apache.org
Using the AOO Java scripting framework to load the ooRexx interpreter via JNI,
the ooRexx interpreter causes a crash while initializing as it receives a null
value when issuing a getenv(PATH). It seems that for unknown reasons the
process environment is not set up properly.

[ooRexx needs the process environment being set up correctly, in order to find
its other pieces to load while initializing.]

As this works flawlessly on 32- and 64-bit Linux and on 32-bit Windows, and
also used to work at least on 32-bit MacOSX in the OOo 3.x days, I assume this
to be a regression.

In the case that someone can spot and fix this on MacOSX, I would like to
propose this as a showstopper bug. Any help to fix this, highly appreciated!

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: 4.1.0_release_blocker requested: [Issue 124509] MacOSX 64 crash in the scripting environment due to getenv(PATH) returning a null value

2014-03-25 Thread Rony G. Flatscher (Apache)
On 25.03.2014 16:10, bugzi...@apache.org wrote:
 r...@apache.org has asked  for 4.1.0_release_blocker:
 Issue 124509: MacOSX 64 crash in the scripting environment due to
 getenv(PATH) returning a null value
 https://issues.apache.org/ooo/show_bug.cgi?id=124509


 --- Additional Comments from r...@apache.org
 Using the AOO Java scripting framework to load the ooRexx interpreter via JNI,
 the ooRexx interpreter causes a crash while initializing as it receives a null
 value when issuing a getenv(PATH). It seems that for unknown reasons the
 process environment is not set up properly.

 [ooRexx needs the process environment being set up correctly, in order to find
 its other pieces to load while initializing.]

 As this works flawlessly on 32- and 64-bit Linux and on 32-bit Windows, and
 also used to work at least on 32-bit MacOSX in the OOo 3.x days, I assume this
 to be a regression.

 In the case that someone can spot and fix this on MacOSX, I would like to
 propose this as a showstopper bug. Any help to fix this, highly appreciated!

 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org
Updated the issue https://issues.apache.org/ooo/show_bug.cgi?id=124509 with a 
list of environment
variables defined when the Java scripting framework executes a script. Maybe 
the names of those
environment symbols (like PYTHONPATH or URE_BOOTSTRAP) may allow to spot the 
code area, where this
gets defined on MacOSX?

---rony


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org