Re: [Xsb-development] compiler bug?

[<ki...@cs...>]

> Now, the problem is that, when the program is compiled and run in the
> same session, conget(aaa,X) binds X to some value other than 0 (in my
> case, 16843008). This value is passed to trie_intern, and used as an
> index to Set_ArrayPtr (which is allocated with size 100), and the
> program segfaults when it tries to access this location.

I think you are right. Thanks, Luis.

Does anyone know why conget isn't set to 0 the first time?
What's the semantics of conget regarding initialization?

I see that on the first try something like

conget(aaa,X)

gives 0. However, if I first do

conset(bbb,2)

in a fresh copy of XSB, then conget(aaa,X) yields some random number.
Why does  psc_prop(Psc, Val0) return a random number for a new atom, if
previously we set psc->data for a different atom?



	--michael