Creating an array gives me a Guru

[Shatterhand]

In my code I have a line that's exactly like this:

Dim map.b(15,375)

It's an array I create to store data read from a file.

when I run the code on Winuae it works flawlessly.

when I try to run on my A600, this line gives me a "Program Failed (error #80000003)" message and then a Guru. Sometimes just a straight reboot+Guru

This is with the debugger on.


if I change it to

Dim map.w(15,375)

I don't get the guru but then the code to read the data from the file and write it in the array doesn't seem to work properly. (all I get is 0s - not discarding I could try to understand why I switch to Words on real hardware I get 0s, but Byes on emulator work)


Anyone has any idea of what's happening? It's really weird for me when code runs on Winuae but then fails on real hardware (and it happens more than I would like)

EDIT: I tried to create the array at the FIRST line of my code, too see if something else done before was the culprit, still got the Guru.

If I make a program with just this line and nothing else I have no problems. What the hell.....

[Don_Adan]

Originally Posted by Shatterhand

In my code I have a line that's exactly like this:

Dim map.b(15,375)

It's an array I create to store data read from a file.

when I run the code on Winuae it works flawlessly.

when I try to run on my A600, this line gives me a "Program Failed (error #80000003)" message and then a Guru. Sometimes just a straight reboot+Guru

This is with the debugger on.


if I change it to

Dim map.w(15,375)

I don't get the guru but then the code to read the data from the file and write it in the array doesn't seem to work properly. (all I get is 0s - not discarding I could try to understand why I switch to Words on real hardware I get 0s, but Byes on emulator work)


Anyone has any idea of what's happening? It's really weird for me when code runs on Winuae but then fails on real hardware (and it happens more than I would like)

EDIT: I tried to create the array at the FIRST line of my code, too see if something else done before was the culprit, still got the Guru.

If I make a program with just this line and nothing else I have no problems. What the hell.....

Odd address error perhaps on 68000 CPU.

[aeberbach]

You are the guru Don Adan... there is no substitute for real hardware.

[Shatterhand]

Any idea of how to solve it?

[Don_Adan]

Originally Posted by Shatterhand

Any idea of how to solve it?

I dont know blitz, but perhaps data must have even length or data must be stored at even addresses. In asembler you use "even" command for this.

[Shatterhand]

Urr.. no idea of how to do that, I think the compiler is supposed to take care of this kind of thing by its own.

I made the rest of the code work with Word instead of Byte, but now it's using double the memory it needs.

This is insanely weird

[meynaf]

You may try something like :

Dim map.b(16,375)

or :

Dim map.b(15,376)

to see if it's alignment problems.

If it doesn't help you'll have to post more of the code, because it's probably not the definition of data that causes the trouble but the actual use of it.

[Toni Wilen]

Originally Posted by Shatterhand

when I run the code on Winuae it works flawlessly.

when I try to run on my A600, this line gives me a "Program Failed (error #80000003)" message and then a Guru. Sometimes just a straight reboot+Guru

Did you have 68000 + more compatible ticked? Only more compatible (and more accurate modes) emulate 68000/010 address errors.

[MickGyver]

You can use the EVEN command also in Blitz Basic, since inline assembly is supported. I don't know if it will fix the problem though.

[Coagulus]

Can you change it to (16,376) and see if that works?

[Shatterhand]

Ok, lots of suggestions , thank you guys, a lot! . I'll only have time to play with my Amiga again in a few days, so it will take a while to test all of this

If it doesn't help you'll have to post more of the code, because it's probably not the definition of data that causes the trouble but the actual use of it.

Actually I tried to make this the very first line of the code and still got the Guru. I get the error when CREATING the array, not when using it. I thought some stuff I was doing before on the code could be creating the error, but even when the first thing the code does is to create this array, I get the same error. It's really very weird.

Did you have 68000 + more compatible ticked? Only more compatible (and more accurate modes) emulate 68000/010 address errors.

Yes, though only now I noticed my "emulated" amiga actually uses an 040. It's an old config I had ready here.

I complained "I get errors on real hardware that I don't get on Winuae" but its probably because of the different configurations.

You can use the EVEN command also in Blitz Basic, since inline assembly is supported. I don't know if it will fix the problem though.

Don't even know how to use Assembly in Blitz, I know its supported, I have no idea of how to use it, I probably should start learning it because I am getting "Use Inline Assembly" as an answer a lot from my Blitz queries

[MickGyver]

Originally Posted by Shatterhand

Don't even know how to use Assembly in Blitz, I know its supported, I have no idea of how to use it, I probably should start learning it because I am getting "Use Inline Assembly" as an answer a lot from my Blitz queries

You just write the assembly code where you want it, it's basically that simple. You can access variables with GetReg (set dX register to value of a variable) and PutReg (set variable to value of a dX register). You can also have statements and functions that are assembly only.

myvar.w=4
GetReg d0,myvar ; d0 will be set to the value of myvar (4)
mulu.w #10,d0 ; inline assembly, multiply d0 with 10
PutReg d0,myvar.w ; myvar will be set to the value of d0 (40)

[Shatterhand]

Shit, it's that simple?

I hoped it would be a very complicated thing, so I could say "Oh that's too much hassle" as an excuse to not learn assembly.

Damn it.

[clenched]

1 - w/68000 CPU most compatible, CE, WinUAE guru happens.
2 - REDDebugger is at fault. The mere act of invoking it, not this array, causes guru.

One error trying to move long word "REXX" to odd. Another trying to go odd w/D0.L. That's enough to consider it a lost cause. This type of crash also plagues one of the tracker libraries.

The only recourse I see is replacing defaultdbug file with the (~32k) one on Blitz2 floppy. It is crude by comparison but does work w/68000.

[E-Penguin]

The annals of computer programming must be littered with stunned developers staring at the screen in disbelief, muttering to themselves "how did this thing ever work?"