Writing FreeDOS programs in C (bugs!)

Throughout the "C Programming" video series, I've been careful to model good programming behaviors. I've stayed inside array boundaries, freed memory after allocating it, and so on. But what happens if you don't follow those programming rules? Let's find out!

Join us on Facebook

Follow us on Twitter

Consider supporting me on Patreon

[gpietsch]

The FreeDOS Edlin source code goes out of its way to get rid of these kinds of errors. Also, first comment!

[Alifrom-Texas]

I am happy I found your channel. Your videos brought so many i am 49 years old now but back in the early computer days I used word perfect, dbase iii plus, lotus 123, PFS Professional write :)

[alexskatkov]

Solid material. Thank you!
What do you think about experimenting with that "garbage" values? I mean, rewriting return adresses with a little dig into asm, for example? Also, program can rewrite some important data close to null, like interrupt vectors or something. I mean, real attempts to hack your programs or OS on that things. I'll be glad if you will put some light on that points. I also heard that it also can be something on double - free mistake. Like, next malloc allocates at same place, but I'm not sure.

[thisisreallyme]

If you're looking for future topic ideas, we might want to dabble in C code that works on both DOS and another environment like Linux, and what options exist in DOS for managing such builds. Cheers!