Searched refs:violations (Results 1 – 25 of 41) sorted by relevance
12
7 # Check whether segmentation violations can be caught using signal handlers.14 …AC_CACHE_CHECK([whether segmentation violations can be caught when using the _AC_LANG compiler], C…38 …[AC_DEFINE([HAVE_CATCHABLE_SEGV], [1], [Define if segmentation violations can be caught using sign…39 …[AC_MSG_WARN([On this platform, segmentation violations cannot be caught using signal handlers. Th…
115 <discard-scope-violations>0</discard-scope-violations>308 <discard-scope-violations>0</discard-scope-violations>
111 <discard-scope-violations>0</discard-scope-violations>
110 <discard-scope-violations>0</discard-scope-violations>
107 <discard-scope-violations>0</discard-scope-violations>
112 <discard-scope-violations>0</discard-scope-violations>
106 <discard-scope-violations>0</discard-scope-violations>
95 <discard-scope-violations>0</discard-scope-violations>
129 <discard-scope-violations>0</discard-scope-violations>
11 the opposite. ld64's behavior hides ODR violations, so we have chosen not
18 violations. This also included rtc, system power off and ON/OFF key.
34 "Report violations of async signal-safety "
43 vulnerabilities are violations of contracts -- in other words, bugs -- anyway.
22 interrupt, used for reporting access violations. The second
50 violations (albeit unable to catch all cases). There are two cases where GNU ld