[Octave-bug-tracker] [bug #44195] segfault with dbstatus

[Rik]

Follow-up Comment #5, bug #44195 (project octave):

On comment #4, it's not which or help, it's the fact that the timestamp on the
file was modified.  When you call an m-file Octave reads it from disk and
converts it to an internal representation and stores the time stamp for when
it did this.  After that the code runs out of memory, but it checks the
function timestamp every time it uses the function to make sure you haven't
been modifying the code.  

When the timestamp does change, regardless of whether any code itself has
changed, Octave throws out the internal representation and re-reads the file
from disk.  Octave doesn't know what you have changed so it deletes
breakpoints and associated information about the function.

    _______________________________________________________

Reply to this item at:

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

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