Re: [Xsb-development] some recent change in attributed variables? (which breaks things)

[David W. <wa...@cs...>]

Michael Kifer writes:

 > > It's failing in mem_dealloc.  Strange.  Nothing I did had anything to
 > > do with memory management.  If you back out my changes, does it work?
 > > I made 2 separate changes, some to emu/biassert.c and some to
 > > syslib/assert.{P,H,xwam}.  Those two sets should be independent.  If
 > > they caused the problem, can you tell me which of these 2 changes?
 > 
 > It is due to your changes to assert.P
 > I backed up to old version 1.37 and things work.
 > 
 > Versions 1.38 and 1.39 (current) don't work.

Ah, so both changes to biassert.c and assert.P.  I think it must be
the biassert.c changes.  Hard to imagine how the assert.P changes did
it.  (You don't ever pass a noninteger as a second argument to
assert/3, do you?  That was the only change I made to assert.P.)

 > If you are within the department then the dept blocks anon cvs
 > (for no good reason).

I'm at XSB and I got it now.  It was pilot error....  I'm actually
tracking down another strange bug in assert, that seems to have been
there longer.  When I find this, I'll go back to looking at yours.
Thanks for the input, and sorry for the problems.

-David