/external/mksh/src/ |
expr.c | 20 * damage or existence of a defect, except proven that it results out
|
syn.c | 21 * damage or existence of a defect, except proven that it results out
|
tree.c | 20 * damage or existence of a defect, except proven that it results out
|
histrap.c | 21 * damage or existence of a defect, except proven that it results out [all...] |
lex.c | 20 * damage or existence of a defect, except proven that it results out [all...] |
shf.c | 22 * damage or existence of a defect, except proven that it results out
|
check.pl | 20 # damage or existence of a defect, except proven that it results out [all...] |
eval.c | 20 * damage or existence of a defect, except proven that it results out [all...] |
exec.c | 20 * damage or existence of a defect, except proven that it results out [all...] |
jobs.c | 20 * damage or existence of a defect, except proven that it results out [all...] |
/external/mockito/src/main/java/org/mockito/ |
Mockito.java | 687 * Also it may reduce defect localization because if stubbed method was not called then no argument is captured. [all...] |
/external/protobuf/src/google/protobuf/ |
wire_format_lite_inl.h | 464 // to avoid this collision appears to be a defect in the standard, but until it [all...] |
/prebuilts/tools/darwin-x86_64/protoc/include/google/protobuf/ |
wire_format_lite_inl.h | 464 // to avoid this collision appears to be a defect in the standard, but until it [all...] |
/external/ImageMagick/ImageMagick/script/ |
advanced-unix-installation.html | 421 <p>If all reasonable corrective actions have been tried and the problem appears be due to a flaw in the configure script, please send a bug report to the <a href="http://www.imagemagick.org/discourse-server/viewforum.php?f=3">ImageMagick Defect Support Forum</a>. All bug reports should contain the operating system type (as reported by <code>uname -a</code>) and the compiler/compiler-version. A copy of the configure script output and/or the relevant portion of <code>config.log</code> file may be valuable in order to find the problem. If you post portions of <code>config.log</code>, please also send a script of the configure output and a description of what you expected to see (and why) so the failure you are observing can be identified and resolved.</p> [all...] |
/external/autotest/contrib/ |
coverage.py | 3 # Perforce Defect Tracking Integration Project [all...] |
/external/clang/test/CXX/drs/ |
dr3xx.cpp | 1084 // FIXME: This is probably a defect. [all...] |
dr4xx.cpp | 1124 // FIXME: Per this DR, these two are valid! That is another defect
|
/external/icu/icu4c/source/test/intltest/ |
utxttest.cpp | [all...] |
/external/libcxx/www/ |
cxx1y_status.html | 109 <!-- <I>Note: "NAD" means that the issue was deemed "Not a defect"</I> --> [all...] |
/frameworks/av/media/libstagefright/foundation/tests/ |
Flagged_test.cpp | 98 * to track if this defect is ever fixed.
|
/packages/services/BuiltInPrintService/jni/lib/ |
wprintJNI.c | [all...] |
/system/core/libpixelflinger/codeflinger/ |
MIPS64Assembler.cpp | 330 // instruction will _also_ use this value (a defect of the simple 1-pass, one- [all...] |
/external/f2fs-tools/tools/sg_write_buffer/ |
sg_cmds_extra.c | 636 /* Invokes a SCSI READ DEFECT DATA (10) command (SBC). Return of 0 -> success 642 static const char * const cdb_name_s = "Read defect(10)"; [all...] |
/device/linaro/bootloader/edk2/StdLib/LibC/Stdio/ |
vfwprintf.c | [all...] |
/external/ImageMagick/www/ |
advanced-unix-installation.html | 425 <p>If all reasonable corrective actions have been tried and the problem appears be due to a flaw in the configure script, please send a bug report to the <a href="http://www.imagemagick.org/discourse-server/viewforum.html?f=3">ImageMagick Defect Support Forum</a>. All bug reports should contain the operating system type (as reported by <code>uname -a</code>) and the compiler/compiler-version. A copy of the configure script output and/or the relevant portion of <code>config.log</code> file may be valuable in order to find the problem. If you post portions of <code>config.log</code>, please also send a script of the configure output and a description of what you expected to see (and why) so the failure you are observing can be identified and resolved.</p> [all...] |