[Octave-bug-tracker] [bug #55939] 'dbstop if error' stops in function str2num, when no error is present

[Floris Van de Vijver]

URL:
  <https://savannah.gnu.org/bugs/?55939>

                 Summary: 'dbstop if error' stops in function str2num, when no
error is present
                 Project: GNU Octave
            Submitted by: fvandevijver
            Submitted on: Sun 17 Mar 2019 10:43:46 AM 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: 5.1.0
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

if a simple str2num command is given, the result is empy, but no error is
thrown; but if 'dbstop if error' command is executed it suddently stops [on
line 62]. 
This looks like unexpected behavior/error

>> str2num('600n')

ans = [](0x0)
>> dbstop if error
>> str2num('600n')
stopped in C:\Octave\OCTAVE~2.0\mingw64\share\octave\5.1.0\m\strings\str2num.m
at line 62
62:   eval (s, "m = []; state = false;");
debug> dbcont
ans = [](0x0




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55939>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/