octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #39063] java: restriction on jvm arguments


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #39063] java: restriction on jvm arguments
Date: Sat, 25 May 2013 15:26:47 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6

Follow-up Comment #3, bug #39063 (project octave):

Did you already try to patch the java package (see my previous comment),
reinstall the patched package and then run it with your desired Java flags?

It would help the devs a lot of you could test the required fix yourself,
especially a fix as simple as the one you seem to need. It it works OK it can
easily be ported to core Octave. (Remember, this is OSS; the best way to get
features & fixes added is to do as much preparatory work as you can do
yourself.)

In that Mathworks web page
http://www.mathworks.de/support/solutions/en/data/1-18I2C/?solution=1-18I2C
you can read that -xm256m is only valid for Java 1.1.8 (i.e., from before the
-X flags). TTBOMK Octave (OF and core) needs Java >= 1.5

I wouldn't say that there's no need to check for invalid options. The Matlab
GUI used to be written in Java - I've found it is easy to crash the entire ML
GUI when experimenting with Java from within ML.
Octave may be more robust but the Java stuff has only recently been absorbed
in core Octave and hasn't received much testing.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39063>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]