<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Segmentation fault - Page 19 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=segmentation_fault&amp;p=18">1.Previous</a><br />
<a accesskey="3" href="page.php?w=segmentation_fault&amp;p=20">3.Next</a>
</p>
<p>platform-dependent actions may also be performed. For example, <a href="page.php?w=Linux">Linux</a> systems using the grsecurity patch may log SIGSEGV signals in order to monitor for possible intrusion attempts using <a href="page.php?w=buffer_overflow">buffer overflow</a>s.</p>

<p>On some systems, like Linux and Windows, it is possible for the program itself to handle a segmentation fault. Depending on the architecture and operating system, the running program can not only handle the event but may extract some information about its state like</p><p>
<a accesskey="1" href="page.php?w=segmentation_fault&amp;p=18">1.Previous</a><br />
<a accesskey="3" href="page.php?w=segmentation_fault&amp;p=20">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
