Searched refs:paranoid (Results 1 – 20 of 20) sorted by relevance
84 public "+1": string = "positive number (for the paranoid)"; // No error86 >"positive number (for the paranoid)" : "positive number (for the paranoid)"
67 public "+1": string = "positive number (for the paranoid)"; // No error
58 public "+1": string = "positive number (for the paranoid)"; // No error
52 large file support, if you are feeling paranoid. Be aware though that
38 If you are (justifiably) paranoid and want to see what 'make install'
738 uint64_t paranoid = 1; in oa_metrics_available() local740 read_file_uint64("/proc/sys/dev/i915/perf_stream_paranoid", ¶noid); in oa_metrics_available()742 if (paranoid == 0 || geteuid() == 0) in oa_metrics_available()
27 - lws-style paranoid response parsing
423 To be paranoid and protect ourselves against this possibility, we almost
3750 are cared in paranoid validation mode only. There are3757 introduced for more paranoid validation in future.3762 New macro to raise an error if in paranoid validation.
275 Modified the TrueType loader to make it more paranoid; this avoids
2436 - zink: be more paranoid about array strides in ntv
2338 - zink: drop paranoid code
4027 - The TrueType glyph loader is now much more paranoid and checks
2811 Add some more logging to GstThread and be a bit more paranoid
5306 Be a bit more paranoid when freeing memory.
7477 Be a bit more paranoid when freeing memory.
6853 # Admittedly, this is quite paranoid, since all the known shells bail6981 # Admittedly, this is quite paranoid, since all the known shells bail
23780 (read_context::load_debug_info): Be paranoid in making sure we
226557 …sys/dvb/gstdvbsrc.*: Fix minor printf format issue; remove overly paranoid checks in create functi…226561 Fix minor printf format issue; remove overly paranoid checks in
116381 Let's be paranoid and make sure we never pass a number that takes up