Quote:
Originally Posted by Toni Wilen
Try H 500, it should list some code. Check also execbase, really unexpected things happen if it gets modified accidentally. (But it should not be possible without debugger complaining
|
FINAL EDIT: - figured out what was going on, see post below -
Without the debugger the app runs ok - constantly loading stuff from disk using the OS, uses the OS for interrupts and keyboard handling. Surely none of that would work if execbase was corrupt?
Edit: H 500 only shows two lines, even though there was quite a lot of code executed.
The current trigger is: "Instruction fetch from memory that was modified", but depending on the config I chose this can be something different.
Even if I do "u", it then seems to break on every instruction when I do "g"
EditEdit: So it seems when running in the debugger something goes through and trashes a bunch of code. It doesn't do this running out of the debugger.