3 ms·
technically, I don't think it's correct to say that C let you bring down the system with one command. On a protected memory system, I think the worst you could
by RockyMcNuts 15y ago
technically, I don't think it's correct to say that C let you bring down the system with one command.
On a protected memory system, I think the worst you could do was a core dump. On Unix, unless you were root, you couldn't hose the system. And if you were root, you didn't need C to do it.
On a DOS, Windows 3.1, Mac machine, yeah, an overrun could freeze your whole system, or just make things go haywire at an unexpected time. Ah... the Mac bomb dialog...fun times. Not remembering exactly what Windows 3.1 did, I don't think the BSOD had been invented yet.
- gcv 15y agowhile (fork()); will cause a world of hurt on a multi-user Unix, even non-root.
- throwaway64 15y agonot if you have sane ulimits on processes, like any multiuser machines should
- kabdib 15y agoI did this once, just to see what would happen. (I hadn't read Lion's notes yet). The admin came running (well, fast-walking) and asked me if I knew what I was doing. "Now I do," I replied. "No, you don't," he said. The next morning there was a photocopy of Lion's Notes on V6 Unix on my desk. I learned a lot from that guy, and that illicit copy of LN.