/external/valgrind/main/none/tests/amd64/ |
ssse3_misaligned.stderr.exp | 0 you should see: "one\ntwo\nthree\n"
|
/external/valgrind/main/none/tests/x86/ |
ssse3_misaligned.stderr.exp | 0 you should see: "one\ntwo\nthree\n"
|
/external/chromium_org/third_party/WebKit/ManualTests/ |
timeout-test.php | 3 ?>This content took 10m10s to deliver. Congratulations, you didn't time out!
|
/external/antlr/antlr-3.4/runtime/Perl5/lib/ANTLR/Runtime/ |
TokenSource.pm | 7 # until you get a good one; errors are not passed through to the parser. 10 # Where are you getting tokens from? normally the implication will simply 28 Errors from the lexer are never passed to the parser. Either you want 29 to keep going or you do not upon token recognition error. If you do not 30 want to continue lexing then you do not want to continue parsing. Just 32 toss you all the way out of the recognizers. If you want to continue 33 lexing then you should not throw an exception to the parser--it has already 34 requested a token. Keep lexing until you get a valid one. Just repor [all...] |
/external/chromium_org/third_party/icu/source/data/translit/ |
trnsfiles.mk | 6 # If you are thinking of modifying this file, READ THIS. 8 # Instead of changing this file [unless you want to check it back in], 9 # you should consider creating a 'trnslocal.mk' file in this same directory. 10 # Then, you can have your local changes remain even if you upgrade or re
|
/external/icu4c/data/translit/ |
trnsfiles.mk | 6 # If you are thinking of modifying this file, READ THIS. 8 # Instead of changing this file [unless you want to check it back in], 9 # you should consider creating a 'trnslocal.mk' file in this same directory. 10 # Then, you can have your local changes remain even if you upgrade or re
|
/external/chromium_org/third_party/icu/source/data/misc/ |
miscfiles.mk | 6 # If you are thinking of modifying this file, READ THIS. 8 # Instead of changing this file [unless you want to check it back in], 9 # you should consider creating a 'misclocal.mk' file in this same directory. 10 # Then, you can have your local changes remain even if you upgrade or re-
|
/external/chromium_org/third_party/icu/source/data/sprep/ |
sprepfiles.mk | 6 # If you are thinking of modifying this file, READ THIS. 8 # Instead of changing this file [unless you want to check it back in], 9 # you should consider creating a 'brklocal.mk' file in this same directory. 10 # Then, you can have your local changes remain even if you upgrade or
|
/external/icu4c/data/misc/ |
miscfiles.mk | 6 # If you are thinking of modifying this file, READ THIS. 8 # Instead of changing this file [unless you want to check it back in], 9 # you should consider creating a 'misclocal.mk' file in this same directory. 10 # Then, you can have your local changes remain even if you upgrade or re-
|
/external/icu4c/data/sprep/ |
sprepfiles.mk | 6 # If you are thinking of modifying this file, READ THIS. 8 # Instead of changing this file [unless you want to check it back in], 9 # you should consider creating a 'brklocal.mk' file in this same directory. 10 # Then, you can have your local changes remain even if you upgrade or
|
/external/mdnsresponder/mDNSShared/ |
dnsextd.conf | 5 // In most cases, you should not need to change these default options in 9 // You need to edit the "zone" statement below to give the name of your 16 // In /etc/named.conf you will need to modify the "options" section to 21 // You also need a "zone" statement in /etc/named.conf to tell BIND the update 23 // network, you might allow anyone to perform updates. To do that, you just 30 // you'll want to limit updates to only users with keys. For example, 31 // you could choose to allow anyone with a DNS key on your server to 42 // You could use a single key which you give to all authorized users, bu [all...] |
/external/chromium_org/third_party/yasm/source/patched-yasm/modules/objfmts/elf/tests/ |
elfglobal.asm | 1 ; Note: you should be able to link elfreloc.o with elfglobal.o to make a
|
/external/stlport/stlport/stl/ |
_ioserr.h | 9 # error STLport iostreams header cannot be used; you chose not to use iostreams in the STLport configuration file (stlport/stl/config/user_config.h).
|
/external/valgrind/main/none/tests/s390x/ |
op_exception.stderr.exp | 8 location. If you are running Memcheck and you just saw a 11 i.e. it's Valgrind's fault. If you think this is the case or 12 you are not sure, please let us know and we'll try to fix it. 21 location. If you are running Memcheck and you just saw a 24 i.e. it's Valgrind's fault. If you think this is the case or 25 you are not sure, please let us know and we'll try to fix it. 34 location. If you are running Memcheck and you just saw [all...] |
/ndk/sources/cxx-stl/stlport/stlport/stl/ |
_ioserr.h | 9 # error STLport iostreams header cannot be used; you chose not to use iostreams in the STLport configuration file (stlport/stl/config/user_config.h).
|
/prebuilts/ndk/5/sources/cxx-stl/stlport/stlport/stl/ |
_ioserr.h | 9 # error STLport iostreams header cannot be used; you chose not to use iostreams in the STLport configuration file (stlport/stl/config/user_config.h).
|
/prebuilts/ndk/6/sources/cxx-stl/stlport/stlport/stl/ |
_ioserr.h | 9 # error STLport iostreams header cannot be used; you chose not to use iostreams in the STLport configuration file (stlport/stl/config/user_config.h).
|
/prebuilts/ndk/7/sources/cxx-stl/stlport/stlport/stl/ |
_ioserr.h | 9 # error STLport iostreams header cannot be used; you chose not to use iostreams in the STLport configuration file (stlport/stl/config/user_config.h).
|
/prebuilts/ndk/8/sources/cxx-stl/stlport/stlport/stl/ |
_ioserr.h | 9 # error STLport iostreams header cannot be used; you chose not to use iostreams in the STLport configuration file (stlport/stl/config/user_config.h).
|
/prebuilts/ndk/9/sources/cxx-stl/EH/stlport/stlport/stl/ |
_ioserr.h | 9 # error STLport iostreams header cannot be used; you chose not to use iostreams in the STLport configuration file (stlport/stl/config/user_config.h).
|
/external/valgrind/main/memcheck/tests/ |
supp_unknown.stderr.exp | 6 If you believe this happened as a result of a stack 8 possible), you can try to increase the size of the
|
/external/valgrind/main/none/tests/linux/ |
blockfault.stderr.exp | 6 If you believe this happened as a result of a stack 8 possible), you can try to increase the size of the
|
/ndk/sources/host-tools/nawk-20071023/ |
README | 30 in FIXES. If you distribute this code further, please please please 31 distribute FIXES with it. If you find errors, please report them 56 This produces an executable a.out; you will eventually want to 60 equivalent), you must compile the pieces manually. We have 62 case you overwrite them. We have also included a copy of 63 proctab.c so you do not need to run maketab. 65 NOTE: This version uses ANSI C, as you should also. We have 72 *if* you provide versions of popen and pclose. The file 76 file makefile.win gives hints on how to proceed; if you run 78 you can subsequently run nmake -f makefile.win. Beware also tha [all...] |
/external/icu4c/data/brkitr/ |
brkfiles.mk | 7 # If you are thinking of modifying this file, READ THIS. 9 # Instead of changing this file [unless you want to check it back in], 10 # you should consider creating a 'brklocal.mk' file in this same directory. 11 # Then, you can have your local changes remain even if you upgrade or
|
/external/chromium_org/third_party/jinja2/_markupsafe/ |
_native.py | 16 sequences. Use this if you need to display text that might contain
|