Turbo C 2.03

[smy]

Hello

I'm looking for Turbo C 2.03 to compile my old Atari ST softwares and release them freely, 30 years later

I have already found the release 2.00, but if someone could provide me with the 2.03 it will be better. Sadly, I can't find my old floppy disks of it (but I have all my source codes !)

Thank you

(I don't know if a request like this one is possible on this forum)

[ThorstenOtto]

You should better use Pure-C (the successor of Turbo-C), which is available for example here viewtopic.php?t=32323

They should be source-compatible, except that the libraries are named pcstdlib etc instead tcstdlib.

[smy]

Thank you. I could successfully compile with Pure-C, with minor updates

[Eero Tamminen]

Thank you. I could successfully compile with Pure-C, with minor updates

Great to hear! Which emulator you're using for development & testing?

[smy]

Thank you. I could successfully compile with Pure-C, with minor updates

Great to hear! Which emulator you're using for development & testing?

Hatari on a Mac M1. A huge gap in 30 years

[Eero Tamminen]

You'll probably already know this, but it's best to tell compiler to include symbol table to the binary, so that they get automatically loaded when you invoke hatari debugger.

And if you enable profiling ("profile on") early on, you will get a backtrace (for the part of the code that ran since last debugger invocation), whenever you invoke debugger.

I would also recommend enabling at least "--trace os_base". When Hatari is already running, you can change trace options, and other things Hatari accepts as command line options, with debugger "setopt" command.

For info on automating above and more, see: https://hatari.tuxfamily.org/doc/debugger.html

PS. You can use NatFeats for very low overhead asserts, and for debug output from things where you cannot normally print anything (e.g. IRQ handlers): https://git.tuxfamily.org/hatari/hatari ... readme.txt

[smy]

You'll probably already know this, but it's best to tell compiler to include symbol table to the binary, so that they get automatically loaded when you invoke hatari debugger.

No, I'm quite new to Atari emulation. My last contact with an Atari was on a real 1040STF in the 90's

Thank you, I'll check that

[Eero Tamminen]

Best is to put the debugger settings you want to use to a separate file, and tell Hatari to use that.

Example "debugger.ini" config file:

Code: Select all

# show VT52 output + GEMDOS Pexec/Fopen calls
trace os_base
# keep track of last executed CPU instruction addresses
history cpu 512
# for backtraces, when symbols are loaded
profile on

Tell Hatari to use that:

Code: Select all

hatari --parse debugger.ini

More examples of common debugger usage: https://hatari.tuxfamily.org/doc/debugg ... e_examples