Re: [Bug-apl] )CHECK and print_stale_info()

[Juergen Sauermann]

Hi David,

this means that an apl value without an owner was detected, but that
no more info about that value is available because the value history was disable.
The history of a value can be enabled with ./configure VALUE_HISTORY_WANTED=yes
or with make develop.

If this happens when )SI is not clear then there is no need for worries.
Otherwise it would be very valuable to know how to reproduce the stale value.

Please note that )CHECK normally frees the stale value, so if you do

       )CHECK
       )SIC
       )CHECK

and get a stale value in the first )CHECK but not in the second, then this
does NOT necessarily mean that the stale value was caused by a non-clear )SI but
that the first )CHECK has dont its job.

/// Jürgen



On 06/27/2014 07:30 PM, David Lamkins wrote:

I sometimes see output from )CHECK similar to the following:

      )check
OK      - no stale functions
print_stale_info():   alloc(Cell.cc:119) flags(MC-)
value history disabled

addr=0x1201eb0 ≡1 ⍴⊏7⊐ flags: 0x0C00   MC- Cell.cc:119
      


OK      - no stale values
OK      - no stale indices

Is the print_stale_info() output expected, a spurious debug output that should be removed, or something else?

Let me know if you'd like me to find a minimal test case to make this happen.

--

"The secret to creativity is knowing how to hide your sources."

   Albert Einstein

http://soundcloud.com/davidlamkins
http://reverbnation.com/lamkins
http://reverbnation.com/lcw
http://lamkins-guitar.com/
http://lamkins.net/
http://successful-lisp.com/