NewsForumsCodeLogsGallerySpecsSearch

Debug THIS!!

BlitzMax Forums/BlitzMax Programming/Debug THIS!!

Who was John Galt?(Posted 2005) [#1]
prog.bmx.d.s
11082: Fixup of -33380 too large for field width of 16 bits

Any idea what this error means anyone?


nawi(Posted 2005) [#2]
It seems that a Fixup, somewhere, is size os -33380, and its too large for a field width of 2 bytes.

Oh and the error occured in line 11082 in prog.bmx.d.s


Who was John Galt?(Posted 2005) [#3]
Smart kid! Leaves me none the wiser.


Perturbatio(Posted 2005) [#4]
some source might help us to help you, otherwise you'll just end up with more wisecracks like that.

although at a guess you could be trying to assign a 32bit (or even 64bit) value to a 16bit variable


Who was John Galt?(Posted 2005) [#5]

For h2:ht=EachIn min_h_list
	If h2.x>h.x-1 And h2.x<h.x+1 And h2.y>h.y-1 And h2.y<h.y+1
		min_h_list.remove(h2)
	EndIf
Next
For h2:ht=EachIn max_h_list
	If h2.x>h.x-1 And h2.x<h.x+1 And h2.y>h.y-1 And h2.y<h.y+1
		max_h_list.remove(h2)
	EndIf
Next


OK - there was a lot of code but narrowed it down -

both lists contain the same type, and it doesn crash if you comment out one or other of these loops (i.e: they both work individually.)


N(Posted 2005) [#6]
Maybe a FlushMem between the two loops would help.

That aside, not a bloody clue what is going on there. It's a given I haven't given much thought to it, but eh.


skidracer(Posted 2005) [#7]
Is this on a Mac?


Who was John Galt?(Posted 2005) [#8]
Noel - Will give it a try.

Skids - Correct.


Who was John Galt?(Posted 2005) [#9]
Tried a flushmem before both these loops and changing all references to h2 to h3 in the second loop - still get the same problem.


Who was John Galt?(Posted 2005) [#10]
Hmmmm- tried to create a cut down working version showing the error - and didn't get an error. Guess I could mail you the whole lot, Skidracer?


Who was John Galt?(Posted 2005) [#11]
Changed some compiler options - turned off

Quick build
Debug build
Build GUI app

And it compiles fine.


marksibly(Posted 2005) [#12]
Hi,

This is a problem with the assembly code generated by the compiler.

I think it's caused by a 'big' block of code in a loop or an If/Then. It's only happening under debug because debug adds extra code, which makes the block even bigger.

I have recently cleaned up debug info quite a bit which will help, but a real fix isn't quite there yet.

In the meantime, you can help by moving stuff out of large blocks into functions.


Who was John Galt?(Posted 2005) [#13]
Thanks Mark, and yeah it was a big block.