[Octave-bug-tracker] [bug #46315] Assertion Failed - profiler crash on every 2nd time execution halts

[Nicholas Jankowski]

Follow-up Comment #2, bug #46315 (project octave):

<from the maintainers list>

The profiler records the time when it enters and exits a function and via
subtraction is able to figure out how much time was spent in the function.  On
entry the profiler records the time and then Octave core determines that the
function has not been parsed so it reads it, but fails to parse it because of
the syntax error.  This means no valid function is created.  When the code
"exits" the function the profiler tries to add the running time to the
profiler dataset  but runs into an assert statement in profiler.cc:391 on the
development branch


assert (call_tree && active_fcn != call_tree);


So, I understand why this is happening, but I don't have a clear idea how to
fix it.  It's not enough simply to remove the assert since there are other
functions involved and other asserts.  Somehow, it would be best for the
profiler to realize that there was a serious error and just abort collecting
statistics on that function.

--Rik

    _______________________________________________________

Reply to this item at:

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

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