🚀 go-pugleaf

Hamish Seaton kirjoitti viestiss� <371FB1B8.9AAA3F68@caverock.net.nz>...
>Could you explain why running say xtree before the my program "fixes" this
>problem?  Would xtree be leaving some instructions behind in memory that my
>program is now pointing to, or would my program be allocated a different
>block of memory which now makes the pointer valid?  Can't understand why
>there seems to be a dependency.

As Pedt Scragg said, a misused interrupt vector is a possible reason.  But I
would say that most probable reason is a pointer to a datastructure which is
used to reference a memory area before it is allocated and thus before the
pointer has received an approppriate value.  Running xtree happens to leave
some non-locking values both for the pointer variable and the memory area it
points.  I have had such bugs made myself.

You didn't tell whether you have the source code.  If you have, search all
pointer variables and follow there flow in program.


Raimo Suonio
raimo.suonio@qdlc.fi (remove spam preventing q)