Pure C debugger with low res program

[sandord]

I'm writing a Pure C program that runs in low resolution. It also disables the mouse.

However, when debugging using the Pure C debugger, the debugger doesn't seem to do anything to keep the mouse working, switch back to medium resolution when showing the debugger etc. So as soon as my program switches to low res and/or disables the mouse, the debugger basically becomes unusable.

Untitled2.png (52.66 KiB) Viewed 4557 times

I've tried playing around with the settings in the debugger (see picture) but it didn't help. Is this a known limitation or am I missing something?

Untitled.png (26.24 KiB) Viewed 4557 times

[stephen_usher]

I take it that you started the debugger when the machine was already booted in low res mode?

[sandord]

I take it that you started the debugger when the machine was already booted in low res mode?

Well, the debugger doesn't let me start it when in low res mode so I started it in medium res. When running my program from the debugger, it (my program) switches to low res.

[stephen_usher]

Oh, that'll be why then. I wonder why it won't start in low res mode. Sounds like a design failure.

[thorsten.otto]

Sounds like a design failure.

Did you ever try to design GEM dialog for low resolution? That's hardly possible in serious programs.

@sandord: you should try to turn off VDI graphics, maybe that helps.

[sandord]

@sandord: you should try to turn off VDI graphics, maybe that helps.

The funny thing is that when I click the checkbox, it doesn't respond. So apparently it cannot be disabled.

[czietz]

Iirc, printed manual or online help (I don't remember which) states that "non-VDI" mode of Pure Debugger can only be used in the high-res mode.

[sandord]

Iirc, printed manual or online help (I don't remember which) states that "non-VDI" mode of Pure Debugger can only be used in the high-res mode.

Thanks, that should explain the disabled checkbox then.

I guess I'm going to need a better debugger But that would probably mean switching compilers

[thorsten.otto]

Iirc, printed manual or online help (I don't remember which) states that "non-VDI" mode of Pure Debugger can only be used in the high-res mode.

That makes sense. Apparently they write directly to the screen otherwise, but only have routines for mono-chrome mode to do so (the Pure-C shell does similar things when you switch to the User-Screen).

That also explains your messed up screen: the VDI is not aware that your program switched the resolution. Maybe you can work around this by catching bus-error yourself, switching back to the original resolution in the handler, and then jump to whatever routine was installed before. That won't help though when trying to set breakpoints, i guess.

[thorsten.otto]

[I guess I'm going to need a better debugger But that would probably mean switching compilers

The only other debugger that i know of than can debug C-Code on a source level basis is gdb, and that only works on MiNT, and only partially. With all others you can just debug the generated assembly code.