HomeSort by relevance Sort by last modified time
    Searched full:errors (Results 176 - 200 of 4729) sorted by null

1 2 3 4 5 6 78 91011>>

  /external/v8/test/mjsunit/
delay-syntax-error.js 28 // To be compatible with JSC syntax errors for illegal returns should be delayed
32 // Do not throw syntax errors for illegal return at compile time.
35 // Throw syntax errors for illegal break and continue at compile time.
39 // Throw syntax errors for illegal return, break and continue at runtime.
  /external/valgrind/main/drd/tests/
annotate_ignore_rw.stderr.exp 9 ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
pth_uninitialized_cond.stderr.exp 10 ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
  /bionic/libc/tools/
checksyscalls.py 156 errors = 0 variable
159 errors = 0
166 errors += 1
169 errors += 1
172 errors += 1
173 return errors
175 errors += check_syscalls("arm", "id", arm_dict)
176 errors += check_syscalls("x86", "id2", x86_dict)
177 errors += check_syscalls("superh", "id3", superh_dict)
179 if errors == 0
    [all...]
  /external/bluetooth/bluez/doc/
oob-api.txt 18 Possible errors: org.bluez.Error.Failed
28 Possible errors: org.bluez.Error.Failed
37 Possible errors: org.bluez.Error.Failed
serial-api.txt 24 Possible errors: org.bluez.Error.InvalidArguments
34 To abort a connection attempt in case of errors or
40 Possible errors: org.bluez.Error.InvalidArguments
service-api.txt 22 Possible errors: org.bluez.Error.InvalidArguments
30 Possible errors: org.bluez.Error.InvalidArguments
41 Possible errors: org.bluez.Error.InvalidArguments
52 Possible errors: org.bluez.Error.InvalidArguments
59 Possible errors: org.bluez.Error.InvalidArguments
agent-api.txt 37 Possible errors: org.bluez.Error.Rejected
48 Possible errors: org.bluez.Error.Rejected
74 Possible errors: org.bluez.Error.Rejected
85 Possible errors: org.bluez.Error.Rejected
93 Possible errors: org.bluez.Error.Rejected
102 Possible errors: org.bluez.Error.Rejected
  /external/chromium/net/base/
cert_status_flags.cc 44 // A certificate may have multiple errors. We report the most
47 // Unrecoverable errors
53 // Recoverable errors
  /external/clang/www/demo/
what is this directory.txt 4 Perhaps it could also be used for getting crash information and details on errors.... I'm not sure if this would require some major changes or not to report this info. Maybe also adding ways that people can use it to test for errors and a way to report such errors would also be good.
  /external/mesa3d/docs/
debugging.html 13 errors. It is up to the application to call
14 <code>glGetError</code> to check for errors. Mesa supports an
30 errors.
  /external/valgrind/main/memcheck/tests/
addressable.stderr.exp 9 For counts of detected and suppressed errors, rerun with: -v
10 ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
38 For counts of detected and suppressed errors, rerun with: -v
39 ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
47 For counts of detected and suppressed errors, rerun with: -v
48 ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
61 For counts of detected and suppressed errors, rerun with: -v
62 ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
80 For counts of detected and suppressed errors, rerun with: -v
82 ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0
    [all...]
partiallydefinedeq.stderr.exp2 2 Currently running on ppc32/64/arm: this test should give 3 errors, not 2.
22 For counts of detected and suppressed errors, rerun with: -v
24 ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
  /libcore/luni/src/main/java/org/xml/sax/
ErrorHandler.java 23 * method. The parser will then report all errors and warnings
27 * register an ErrorHandler, XML parsing errors will go unreported,
28 * except that <em>SAXParseException</em>s will be thrown for fatal errors.
29 * In order to detect validity errors, an ErrorHandler that does something
32 * <p>For XML processing errors, a SAX driver must use this interface
35 * errors and warnings. Note, however, that there is no requirement that
36 * the parser continue to report additional errors after a call to
39 * Also parsers may throw appropriate exceptions for non-XML errors.
41 * an IOException for errors accessing entities or the document.</p>
56 * are not errors or fatal errors as defined by the XM
    [all...]
  /prebuilt/linux-x86/toolchain/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/sys/
xattr.h 39 is SIZE bytes long). Return 0 on success, -1 for errors. */
46 Return 0 on success, -1 for errors. */
52 bytes long). Return 0 on success, -1 for errors. */
57 SIZE bytes long). Return 0 on success, -1 for errors. */
63 Return 0 on success, -1 for errors. */
68 bytes long). Return 0 on success, -1 for errors. */
74 errors. */
80 last pathname component. Return 0 on success, -1 for errors. */
85 LIST (which is SIZE bytes big). Return 0 on success, -1 for errors. */
90 on success, -1 for errors. *
    [all...]
  /external/libnfc-nxp/src/
phHciNfc_RFReader.h 123 * \retval Other errors Errors related to the other layers
147 * \retval Other errors Errors related to the other layers
200 * \retval Other errors Errors related to the other layers
226 * \retval Other errors Errors related to the other layers
246 * \retval Other errors Errors related to the other layer
    [all...]
phHciNfc_Sequence.h 186 * \retval Other errors Other related errors
212 * \retval Other errors Other related errors
239 * \retval Other errors Other related errors
266 * \retval Other errors Other related errors
292 * \retval Other errors Other related errors
    [all...]
  /external/chromium/chrome/browser/ssl/
ssl_error_info.h 46 // Populates the specified |errors| vector with the errors contained in
47 // |cert_status|. Returns the number of errors found.
48 // Callers only interested in the error count can pass NULL for |errors|.
52 std::vector<SSLErrorInfo>* errors);
  /external/clang/test/Index/
complete-driver-errors.c 9 // CHECK-DIAGS: complete-driver-errors.c:1:6:{1:13-1:14}: warning: incompatible integer to pointer conversion initializing 'int *' with an expression of type 'int'
11 // Test driver errors with code completion
15 // Test driver errors with parsing
18 // CHECK-LOAD: complete-driver-errors.c:1:6: VarDecl=blah:1:6
20 // Test driver errors with code completion and precompiled preamble
  /external/freetype/include/freetype/
fterrdef.h 32 /* generic errors */
58 /* glyph/character errors */
77 /* handle errors */
98 /* driver errors */
105 /* memory errors */
112 /* stream errors */
131 /* raster errors */
142 /* cache errors */
147 /* TrueType and SFNT errors */
206 /* CFF, CID, and Type 1 errors */
    [all...]
  /libcore/luni/src/main/java/javax/xml/transform/
ErrorListener.java 26 * <code>Transformer</code> then reports all errors and warnings through this
31 * is used which reports all warnings and errors to <code>System.err</code>
35 * errors.</p>
37 * <p>For transformation errors, a <code>Transformer</code> must use this
40 * different types of errors and warnings. Note however that the
45 * errors as well as transformation errors.</p>
53 * conditions that are not errors or fatal errors. The default behavior
76 * application to process the document through to the end if no other errors
    [all...]
  /external/bluetooth/glib/docs/reference/glib/tmpl/
error_reporting.sgml 5 a system for reporting errors
10 GLib provides a standard method of reporting errors from a called function to
21 recoverable runtime errors, never to report programming errors.</emphasis> If
25 <emphasis>only</emphasis> be used for programming errors, it should not be used
30 Examples of recoverable runtime errors are "file not found" or "failed to parse
31 input." Examples of programming errors are "NULL passed to strcmp()" or
32 "attempted to free the same pointer twice." These two kinds of errors are
33 fundamentally different: runtime errors should be handled or reported to the
34 user, programming errors should be eliminated by fixing the bug in the program
    [all...]
  /dalvik/dx/src/junit/framework/
TestResult.java 9 * The test framework distinguishes between <i>failures</i> and <i>errors</i>.
10 * A failure is anticipated and checked for with assertions. Errors are
30 * Adds an error to the list of errors. The passed in exception
76 * Gets the number of detected errors.
82 * Returns an Enumeration for the errors
84 public synchronized Enumeration errors() { method in class:TestResult
  /external/clang/utils/
SummarizeErrors 47 errors = multidict()
51 d = errors
56 errors = errors.items()
83 (errors, 'Errors'),
  /external/e2fsprogs/tests/
README 9 0 No filesystem errors were detected
10 1 Filesystem errors detected, but corrected
12 4 Filesystem errors left uncorrected
23 filesystem with no detectable errors found in the second pass. The
24 exception is the okgroup.img filesystem, which contains no errors, and
29 errors. So if you modify the test_script to try running these

Completed in 1324 milliseconds

1 2 3 4 5 6 78 91011>>