Re: [hatari-devel] Magic again : gemdos question

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

On maanantai 30 tammikuu 2012, Eero Tamminen wrote:
> You can debug the info further by checking what these show:
> - "info gemdos" -> GEMDOS HD emu DTA table contents
> - "info basebase" -> check contents from "Process DTA" address
....
> PS. Another problem could be if some path was longer than:
> 	MAX_GEMDOS_PATH 256
> 
> But your case didn't seem like that.

To debug internal memory corruption:

* Before Hatari build, install mudflap library development package,
  typically it's named either "libmudflap<version>-<gcc-version>-dev"
  (e.g. libmudflap0-4.4-dev in Debian Squeeze) or "libmudflap-devel"
  (e.g. in Fedora).

* Enable ENABLE_MUDFLAP CMake option and rebuild.

The run Hatari again with sound (and anything else using threads)
disabled.  It's very slow, but should catch most array overwrites.


	- Eero