I removed the optimize switch, and that helped it compile. Unfortunately, it didn't help the original bug. Thanks, Paul Ullrich von Bassewitz wrote: >On Mon, Nov 21, 2005 at 11:26:37AM -0600, PH wrote: > > >>The instruction at 0x0042702f referenced memory at 0x00000020. The >>memory could not be read. >> >> > >I think it's the same error that Oliver has already reported. The Linux >version seems to work fine even when running under valgrind. So I will have to >boot the windows machine to search for the problem, which is somewhat more >work. I would be glad if you could retry once the windows problem is fixed. As >a quick workaround, disable optimization. The bug is caused somewhere in the >optimizer (if it's the same bug). > >Regards > > > Uz > > > > ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Mon Nov 21 20:04:23 2005
This archive was generated by hypermail 2.1.8 : 2005-11-21 20:04:25 CET