[Top][All Lists]

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

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

From: Rik
Subject: [Octave-bug-tracker] [bug #44195] segfault with dbstatus
Date: Fri, 06 Feb 2015 19:06:30 +0000
User-agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1)

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:


  Message sent via/by Savannah

reply via email to

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