1. RE: odd error with read_bitmap()
> posted by: CoJaBo <cojabo at suscom.net>
>
> Sounds like you are reading/writing outside the allocated memory,
> I did that once and got completly random results.
> Try using the trace feature in Eu,
> the last line in the file should be the one that caused the crash.
I am just showing a bitmap on the screen. I think maybe the interpreter
is writing into the variable memory space.
It is quite consistant. My program runs fine, then gives me a type check
error when I return to the interpreter.
If I run my program again, windows aborts it. I have the public domain
version, so I can't trace. I test the
value of my sequence in the program and it is ok. After the program
runs, the interpreter says my sequence has the
value of 1, but I don't give it that value anywhere, so how does it get
that value, if not a bug in the interpreter?
My bitmap is a full screen picture in mode 261, 256 colors, so it is
quite big. It is my opening screen. Then I switch
to text mode and don't use it again.
That was yesterday. Today:
I had declared the sequence outside of the subroutine, so I tried
declaring it inside the subroutine to see if that
made any difference. The program ran fine, but when returning to the
interpreter, it told me that my err.ex referred
to the test file I ran yesterday. It was not even in the interpreter's
memory today. Why would that happen?
JOHN
2. RE: odd error with read_bitmap()
John McAdam wrote:
>
<snip>
> That was yesterday. Today:
>
> I had declared the sequence outside of the subroutine, so I tried
> declaring it inside the subroutine to see if that
> made any difference. The program ran fine, but when returning to the
> interpreter, it told me that my err.ex referred
> to the test file I ran yesterday. It was not even in the interpreter's
> memory today. Why would that happen?
Hard to say. Could you post the code (preferably a minimal example)?
Matt Lewis
