| |||||||||||||
|
| |||||||||||||
How to kill a web browserHow to kill a web browserPosted Oct 22, 2004 0:10 UTC (Fri) by JoeBuck (subscriber, #2330)In reply to: How to kill a web browser by nix Parent article: How to kill a web browser Almost all of the GCC crashes occur when GCC itself detects an inconsistency and quits with an internal error. There are a few, though, where the compiler actually crashes because of internal corruption, but those are far rarer. Cases where the application itself decides to abort aren't security risks (though they could possibly be used to create a denial of service attack if the app can be made to repeatedly shut itself down).
(Log in to post comments)
How to kill a web browser Posted Oct 22, 2004 13:45 UTC (Fri) by nix (subscriber, #2304) [Link] 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 :) )
|
|
||||||||||||