Quote:
Originally Posted by hooverphonique
Ok, I was wrong. I took the vasm output as gospel:
But it turns out that my output executable is 362kB due to the vasm "-linedebug" option. I guess I need to find a way to disable debug symbol generation for data sections, because it bloats the executable and is probably not really useful.
|
I noticed the slow debug loading when my exes were getting past a certain size. Also they use more memory to load so I have to add more fast ram than usual even if I'm targeting an A500 512KB. As a workaround I've configured my "debug" settings to use the config "A4000/040" model and that loads instantly. Not ideal but as I want my stuff to work on that config as well anyway and I only used debug to "fix" problems it works ok.