Searched refs:rogue (Results 1 – 25 of 28) sorted by relevance
12
82 int notlifo, rogue; /* counts of non-LIFO frees and rogue frees */ member165 zone->rogue++; in mem_free()184 zone->rogue = 0; in mem_setup()246 if (zone->rogue) in mem_done()248 << zone->rogue << " frees not recognized" in mem_done()
67 int notlifo, rogue; /* counts of non-LIFO frees and rogue frees */ member150 zone->rogue++; in mem_free()169 zone->rogue = 0; in mem_setup()225 if (zone->rogue) in mem_done()227 prefix, zone->rogue); in mem_done()
73 int notlifo, rogue; /* counts of non-LIFO frees and rogue frees */ member154 zone->rogue++; in mem_free()172 zone->rogue = 0; in mem_setup()224 if (zone->rogue) in mem_done()226 prefix, zone->rogue); in mem_done()
19 rogue server could send you the name of a DLL or other file that could possibly
150 if (zone->rogue)152 - prefix, zone->rogue);154 + << zone->rogue << " frees not recognized"
197 Relative to setting rogue parameters; see section [req-introspection].
844 Users **SHOULD** be able to modify rogue parameters through the native API at846 <why>Otherwise, a rogue parameter is of no use.</why>
30 …in case a device becomes compromised by a malicious guest. For example, a rogue device that is abl…
466 without interferences with rogue clients. Note that there are no566 it needs to be exported for rogue clients.713 support rogue clients compiled against 2.1.7 to work correctly.1682 Intel, as reported by Sean McBride <sean@rogue-research.com> on
1911 2014-03-18 Sean McBride <sean@rogue-research.com>1956 2014-03-09 Sean McBride <sean@rogue-research.com>2002 2014-03-06 Sean McBride <sean@rogue-research.com>2029 2014-03-04 Sean McBride <sean@rogue-research.com>2226 2014-02-08 Sean McBride <sean@rogue-research.com>
386 Reported by Sean McBride <sean@rogue-research.com>.3406 Reported by Sean McBride <sean@rogue-research.com>.3499 2009-01-06 Sean McBride <sean@rogue-research.com>5138 2007-12-04 Sean McBride <sean@rogue-research.com>5861 2007-06-01 Sean McBride <sean@rogue-research.com>7920 used to detect rogue clients from 4 to 16. This is to prevent some
4908 the first cmap subtable always under rogue-compatible5747 Restrict the number of the charmaps in a rogue-compatible mode.5751 minimum character code passed by a legacy rogue client by...5754 undefined (thus the rogue client compatibility is not required).
2572 command. Consequently, a number of rogue clients which directly2576 We provide patches for most of those rogue clients. See the2579 https://www.freetype.org/freetype2/patches/rogue-patches.html2631 subglyph data. This can be used by rogue clients which used to
128 - Add support for reining in rogue fuzzer passes (#3987)
43 - Add support for reining in rogue fuzzer passes (#3987)
1239 - Avoid accessing font tables during face destruction, in casce rogue
600 rogue kerning values and variations for random classes against class zero (everything
12407 rogue
1a 2A 3Aaron 4AARON 5abaissiez 6abandon 7abandoned 8abase 9Abase 10 ...
14909 ph,san rogue,San Rogue,11,,10.091903,124.322621
919 stops rogue patterns using up too much system stack when being com-