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

[Nicholas Jankowski]

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

so, following up on Rik's comment:

So profiler throws a fit when it gets called again after being stopped short
the first time. so it didn't seem to get the chance to 'reset itself'. 

A couple questions:

1 - why a crash (with the odd text parsing) versus just an execution halt? Is
that normal for his type of error?

2 - Calling 'profile off' from the command line before calling the offending
function again does completely avoid the crash. Calling profile off as the
first line within the offending script does not. I think one of the other bug
reports mentioned something about 'profile' expecting to be called from the
command line rather than in a script...

3 - removing the profile off line at the start of the script avoids the crash,
but only because the 'profile on' call generates the usual 'Can't reset active
profiler' error.

4 - removing both the off and on commands allows the profiler to run
indefinitely. it never gets to a profile off statement, but never has any
issue with the function with the syntax error, even or repeated calls.

it's #4 that seems a bit odd to me. it's specifically something about the
profile off/profile on call that causes the crash, but only if the profile off
is called within the script. So the profiler has no problem with the aborted
execution in general. but trying to start a new profiler call (with the
profile on), after a previous crash breaks things.

Is the profile off call not properly 'cleaning the slate' for the second
profile on call?  What's left that is different?


    _______________________________________________________

Reply to this item at:

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

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