Question: When execution point hits a kernal routine, the IDE pops-up "Unable to open 'DISKIO.s': Unable to read file"

[johnlivdahl]

I have a c project and when execution hits a kernal routine, the following happens:

Popup in IDE
Unable to open 'DISKIO.s': Unable to read file 'c:\Users\jlivd\OneDrive\c64\cc65_Projects\DISK_IO\DISKIO\src\DISKIO.s' (Error: Unable to resolve non-existing file 'c:\Users\jlivd\OneDrive\c64\cc65_Projects\DISK_IO\DISKIO\src\DISKIO.s').

There is no such file in my project but there is a DISKIO.c that is working until a kernal routine is hit.
I can't see how to config the debugger not to look for source files for kernal ROM routines.

I would like a way to be able to view the disassembly when the code is outside of the project's symbol range. When the debugger is active I can't use vices monitor to see where the kernal is stuck (it appears the IEC routines don't like being stepped over.)

[empathicqubit]

I'm not sure why it would do that. Can you link your project?

[empathicqubit]

Also, if possible can you use a screen recorder such as Screenity to take a video of the steps you're taking?

I would like a way to be able to view the disassembly when the code is outside of the project's symbol range. When the debugger is active I can't use vices monitor to see where the kernal is stuck (it appears the IEC routines don't like being stepped over.)

Something different than the text monitor that appears in the terminal tab? I need an idea of what you're envisioning.

If you are manually stepping through the code in the text monitor and the current execution point does not match the beginning of a C statement, it may try to point to a file that doesn't exist. The easiest way to fix this is to include those files in your build by running cc65 with the -S switch after your regular build command. Do not run it before the regular compile because that will create and then immediately destroy those files.