[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #51845] Variable editor: trying to open Java o
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #51845] Variable editor: trying to open Java or COM objects leads to infinite loop & crash |
Date: |
Fri, 25 Aug 2017 09:36:54 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 |
URL:
<http://savannah.gnu.org/bugs/?51845>
Summary: Variable editor: trying to open Java or COM objects
leads to infinite loop & crash
Project: GNU Octave
Submitted by: philipnienhuis
Submitted on: Fri 25 Aug 2017 03:36:53 PM CEST
Category: GUI
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Segfault, Bus Error, etc.
Status: None
Assigned to: None
Originator Name: Philip Nienhuis
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: Microsoft Windows
_______________________________________________________
Details:
Provisionally only Windows but I think this also happens on Linux.
Steps to reproduce:
a = javaObject ("java.lang.Double", 1.5);
##right-click a in workspace, or do
openvar (a)
and in the command window we get an endless loop of
:
>> error: [java] java.lang.IllegalArgumentException: not a Java array
error: parse error
>> error: [java] java.lang.IllegalArgumentException: not a Java array
error: parse error
>> error: [java] java.lang.IllegalArgumentException: not a Java array
error: parse error
:
Ctrl-C doesn't help (reliably). Closing Octave's GUI using the close button
does, but then Octave crashes upon exit.
Similar behavior goes to COM objects (in Windows).
I haven't tried this with other objects (classdef etc.) but I suspect there it
will also go wrong.
When the variable Editor was still just a patch I thought that limiting the
function openvar (that is called when right-clicking & selecting "Open in
Variable Editor" in the workspace) to only accept some types of variables
(prvisionally just numeric, cell, text and struct) would be the best option to
avoid this bug. Later on when the variable Editor could handle more types
openvar could be adapted accordingly.
But I couldn't find out how to get this together (due to lacking C++/Qt
skills).
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51845>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #51845] Variable editor: trying to open Java or COM objects leads to infinite loop & crash,
Philip Nienhuis <=