[prev] [thread] [next] [lurker] [Date index for 2007/01/29]
On Sun, Jan 28, 2007 at 07:39:33PM -0500, Sean Conner wrote: > It was thus said that the Great Yossi Kreinin once stated: > > Exceptions and error codes aside, people who trap SIGSEGV should be shot. > > Oh, come on now ... how else do you expect us to reattempt the operation > using a different algorithm? Fwiw, I use a program now and then that has a perfectly good rason to ignore SIGSEGV. Basilisk2, the Mac 68k emulator, has an option to trap memory access exceptions. This is because on some platforms (Linux included) it has support for directly mapping the memory space of the 68k pretend-machine onto the unix virtual process space, which has a really huge effect on execution speed. It seems that in the 68k Mac MMUless land, since things like accessing location 0x00000 was not caught by any hardware, all kinds of shipped software did so on a regular basis. Games, productivity apps, Apple-provide control panels. You name it. Without the trap, the emulated environment has a remarkably short lifespan. There is the mitigating factor that I don't really care much about the data in this little playpen. Retro-hate? -joshThere's stuff above here
Generated at 23:01 on 06 Feb 2007 by mariachi 0.52