[comp.sys.ibm.pc] C/disk Danger

mac3n@babbage.acc.virginia.edu (Alex Colvin) (02/15/88)

> > had Quick C blow away hard drives, so be careful.
> I know of a case where MSC (4.0 I think) utterly scrambled a hard drive

Please note!  This has nothing to do with any C compiler.  This has to do
with system tables living in unprotected memory, down in the low addresses
that are usually generated by mistakes.

There's not much you can do about this except to be extremely careful or
program in some language that doesn't allow/require you to screw around
with pointers, e.g.  Pascal or BASIC.  Naive programmers shouldn't use C.
See many of the pointer questions here and on comp.lang.c.

Also part of the problem here is the object file format, which doesn't
provide the linker enough information to detect a screwup in memory
models.  Does anyone else wind up renaming their files *.obs and *.obb?