| |||||||||||||
|
| |||||||||||||
How to kill a web browserHow to kill a web browserPosted Oct 22, 2004 13:45 UTC (Fri) by nix (subscriber, #2304)In reply to: How to kill a web browser by JoeBuck Parent article: How to kill a web browser
The internal-corruption crashes certainly are rare, now. I was really thinking of the days of egcs and before, when the `bailing out' message often *was* the result of a SIGSEGV being caught, if memory serves, and was really rather easy to trigger...
... and no, this isn't a security risk. (Who would execute a compiler in a security-critical environment anyway? The security risks are generally in the compiler's output when it succeeds :) )
(Log in to post comments)
|
|
||||||||||||