bugGNU Octave - Bugs: bug #48012, bug #39063: apply fix to allow...

 
 

bug #48012: bug #39063: apply fix to allow arbitrary jvm options on the stable branch

Submitter:  Ernst Reissner <ernstreissner>
Submitted:  Wed 25 May 2016 01:48:56 PM UTC
   
 
Category:  Libraries Severity:  1 - Wish
Priority:  3 - Low Item Group:  Feature Request
Status:  Fixed Assigned to:  None
Originator Name:  ErnstReissner Open/Closed:  * Closed
Release:  * 4.0.0 Operating System:  * Any
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 27 May 2016 02:22:19 PM UTC, comment #5: 

I grafted the changeset from default to stable and merged back with default.

Yes, there will likely be a 4.0.3 release soon.

John W. Eaton <jwe>
Group administrator
Fri 27 May 2016 02:21:26 AM UTC, comment #4: 

Ernst: it was definitely fixed on the development branch (in November 2015), and has never been released with any 4.0.x yet.

It seems like an easy fix to apply on the stable branch if this is important. Someone who wants to do so should apply it on stable and make sure to merge cleanly with the default branch.

I don't know if or when a 4.0.3 release will happen.

I've reopened and retitled this bug for that purpose.

Mike Miller <mtmiller>
Group Member
Thu 26 May 2016 08:33:30 PM UTC, comment #3: 

currently, 4.0.2 is out.
It would be nice to have it available with 4.0.3.
I think, it was already fixed and got broken later,
I cannot imagine how.
There is simply too much code written. That is all.

So I would vote as Philip does.
Can I contribute anything to a quick fix?
My problem is that I have sporadic bugs
because of overflow of ints which are all guarded by assertions.
(adding two non-negative numbers are asserted to be non-negative again. )
That way the application stops outputting a message
but only if -ea flag is set.
This in turn is currently not passed by octave to java.

Would it be possible to reopen that bug report?

Ernst Reissner <ernstreissner>
Thu 26 May 2016 08:04:41 PM UTC, comment #2: 

Given that this is such a simple an -AFAICS- non-intrusive fix, can it be backported? or will there be no 4.0.4 release?

4.2.x can be a long time away.

Philip Nienhuis <philipnienhuis>
Group Member
Wed 25 May 2016 03:29:52 PM UTC, comment #1: 

The fix for bug #39063 was applied on the development branch that will become Octave 4.2, it has not yet been released.

Mike Miller <mtmiller>
Group Member
Wed 25 May 2016 01:48:56 PM UTC, original submission:  

The Problem reoccurred in 3.8.2 at least and is also present in 4.0.0.

It is simple to do a d vital that octave does no checking but leaves checks to jvm.

Ernst Reissner <ernstreissner>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Digest:
   bug dependencies.

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by ernstreissner (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 9 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-05-27 jwe StatusDuplicate Fixed
        Open/ClosedOpen Closed
    2016-05-27 mtmiller Severity3 - Normal 1 - Wish
        Priority5 - Normal 3 - Low
        Open/ClosedClosed Open
        Summarybug #39063: java: restriction on jvm arguments: coould not reset to open bug #39063: apply fix to allow arbitrary jvm options on the stable branch
    2016-05-25 mtmiller Dependencies- Depends on bugs #39063
    2016-05-25 mtmiller StatusNone Duplicate
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code