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

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

[Octave-bug-tracker] [bug #64849] Octave throws an 'error: add_breakpoin


From: anonymous
Subject: [Octave-bug-tracker] [bug #64849] Octave throws an 'error: add_breakpoints_in_function' under certain conditions
Date: Fri, 3 Nov 2023 07:07:54 -0400 (EDT)

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

                 Summary: Octave throws an  'error:
add_breakpoints_in_function' under certain conditions
                   Group: GNU Octave
               Submitter: None
               Submitted: Fri 03 Nov 2023 11:07:52 AM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: GNU/Linux
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Fri 03 Nov 2023 11:07:52 AM UTC By: Anonymous
I have a sub-directory which contains an OCT compiled function. This function
shadows the core function common_size (I am aware of the implications).

Case a) throws error
====================
When octave is started, a pkg (it could be any!) is loaded, the sub-directory
added (which gives correctly a warning) and then the function is called the
FIRST time, octave throws an error:
  

pkg load io;
addpath("./OCT");
[a1,a2,a3] = common_size(1,1);


results in 


warning: function ..../OCT/common_size.oct shadows a core library function
error: add_breakpoints_in_function: unable to find function 'common_size'




When the same command is executed on the command line after the error for a
SECOND time, it works without throwing an error and any times afterwards.

[a1,a2,a3] = common_size(1,1)
a1 = 0
a2 = 1
a3 = 1



case b) works without any problems
==================================
When no package is loaded after octave start, it works without any problem:

addpath("./OCT");
[a1,a2,a3] = common_size(1,1);


warning: function ..../OCT/common_size.oct shadows a core library function
a1 = 0
a2 = 1
a3 = 1










    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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