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

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

[Octave-bug-tracker] [bug #50732] infinite error loop when assigning a s


From: Hartmut
Subject: [Octave-bug-tracker] [bug #50732] infinite error loop when assigning a strel (class) object to a vector
Date: Wed, 5 Apr 2017 13:20:45 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

URL:
  <http://savannah.gnu.org/bugs/?50732>

                 Summary: infinite error loop when assigning a strel (class)
object to a vector
                 Project: GNU Octave
            Submitted by: hardy
            Submitted on: Wed 05 Apr 2017 05:20:43 PM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.1
        Operating System: Any

    _______________________________________________________

Details:

Here is how to reproduce the behavior:

clear
pkg load image

se = strel ("square", 1);
vec(1)=se;
vec(2)=se;  


As a result I get an infinite stream of error messages like this:

[...]
error: parse error
error: called from
    print_usage at line 91 column 5
    size at line 31 column 3
error: Invalid call to isempty. Correct usage is:

-- isempty (A)
error: parse error 
[...and so on...]


This happens with Octave 4.2.1 and image-2.6.1 (both current releases). I have
seen this under Linux (Ubuntu 16.04) as well as under Windows (7).

I am not sure if this is a bug in the definition of the strel (class) object
(this would be part of the image package). Or if this in a bug in core Octave.
But even if there is something ill-defined with the (image package) strel
object, I think core Octave should just throw one error message and then stop.
The current behavior of starting an infinite loop of error messages cannot be
right on the (core) Octave side. This loop of error messages can NOT even be
stopped by hitting Ctrl-C.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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