|
From: | Rik |
Subject: | Re: profiler crash |
Date: | Wed, 28 Oct 2015 10:01:50 -0700 |
On 10/28/2015 09:00 AM,
address@hidden wrote:
Nick, Please add this to the bug tracker as jwe suggests. It is fairly easy to understand what is happening at a macro level. 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 |
[Prev in Thread] | Current Thread | [Next in Thread] |