Re: move constructors

[John W. Eaton]

On 8/15/19 5:52 PM, John W. Eaton wrote:
> On 8/15/19 4:33 PM, Rik wrote:
>
> > For reference, how did you determine which
> > functions were causing the calls?  A debugger and a breakpoint in
> > ~octave_value_list()?
>
> Yes, I used
>
>    ./run-octave -g -cli
>
> and let the interpreter get to the command prompt.  Then C-c to get to 
> the (gdb) prompt, then set a breakpoint at 
> octave_value_lists::~octave_value_list.  Then executed something like 
> "sin(1);" and looked at stack traces each time the breakpoint was hit.

Also, this was with a modified octave_value_list destructor that printed 
a message.  So I also stepped through the code after the first 
breakpoint was hit and watched for the status messages to be printed 
from the destructor.  That is a little faster than looking at stack 
traces for each call to the destructor.

jwe