Is there a way to source debug a msx program writtin in c:
1. Does a c debugger exist for MSX-c?
2. Does a c debugger exist for sdcc (cross (windows) platform debugging)?
3. Does a c debugger exist for Hi-Tech c (msx platform and cross (windows) platform debugging)?
4. How to get a (free/paid) copy of the msdos version of Hi Tech C v7.8pl2?
Thanks
Для того, чтобы оставить комментарий, необходимо регистрация или !login
Is there a way to source debug a msx program writtin in c:
1. Does a c debugger exist for MSX-c?
2. Does a c debugger exist for sdcc (cross (windows) platform debugging)?
3. Does a c debugger exist for Hi-Tech c (msx platform and cross (windows) platform debugging)?
A debugger runs against the compiled code, so it doesn't matter whether the original program was written in MSX-C, SDCC, Pascal, or directly in assembler.
I use ASCII's MSX-SBUG2, which is part of the same set of development tools as MSX-C and MSX-DOS2 TOOLS.
In my opinion, there are two kinds of debuggers: (1) a source-level debugger, typically seen in integrated development environments and (2) a machine-language debugger. MSX-SBUG2 looks like a machine-language debugger. A machine-language debugger makes it difficult to pinpoint a bug in your c source (z80 assembly to c). Or am I missing something?
In my opinion, there are two kinds of debuggers: (1) a source-level debugger, typically seen in integrated development environments
You won't find any realtime syntax highlighters / live parsers for MSX.
Bit Addict wrote:
and (2) a machine-language debugger. MSX-SBUG2 looks like a machine-language debugger. A machine-language debugger makes it difficult to pinpoint a bug in your c source (z80 assembly to c). Or am I missing something?
To my knowledge, that's the kind of debugger you'll find on 8-bit platforms.
I wonder how much effort it would take to get SDCC's source level debugger 'sdcdb' to work.
For the MSX I use the old fashioned way by using print statements in my code. When using a graphics mode this is not so convenient. I use OpenMSX for development and then I can use the debug peripheral where I send the textual output to.
Correct me if I am wrong, but "source-level" debuggers require some kind of "markers" added by the compiler and may not be able to work after compiler optimizations. So, I don't think this exists for MSX.
For asm development, the openMSX-debugger is now unbeatable. But I also have the same curiosity about source-level debuggers for C for the MSX. That would be lovely, because debugging with printf isn't productive at all.
For the Hitech-C for DOS I know there's the Lucifer remote debugger. In theory you have to compile it run it on the target system, then you'll be able to do remote debugging via RS-232C.
But an open source alternative like that for SDCC would be excellent.
