Home
last modified time | relevance | path

Searched refs:crash (Results 1 – 25 of 690) sorted by relevance

12345678910>>...28

/external/v8/test/mjsunit/regress/
Dregress-crbug-134055.js30 function crash(obj) { function
48 crash(a); // Premonomorphic.
49 crash(a);
50 crash(b);
51 crash(c);
52 crash(d); // Polymorphic, degree 4.
62 %OptimizeFunctionOnNextCall(crash);
63 crash(a);
Dregress-crbug-350434.js15 function crash(o, timeout) { function
26 crash(o, 100000);
27 crash(o, 100000);
28 crash(p, 100000);
29 %OptimizeFunctionOnNextCall(crash);
30 crash(o, 100000);
33 crash({}, 0);
Dpost-increment-close-context.js31 function crash() { function
34 assertFalse(crash());
36 %OptimizeFunctionOnNextCall(crash);
37 assertFalse(crash());
39 assertTrue(crash());
41 assertFalse(crash());
Dregress-crbug-196583.js42 function crash(obj) { function
47 crash(a);
48 crash(b);
49 crash(c);
51 %OptimizeFunctionOnNextCall(crash);
52 assertEquals(1, crash(a));
Dregress-crbug-285355.js36 function crash(array) { function
40 assertEquals(2, crash(new Array(1)));
41 assertEquals(2, crash(new Array(1)));
42 %OptimizeFunctionOnNextCall(crash)
43 assertEquals(2, crash(new Array(1)));
Dregress-crbug-258519.js35 function crash(x) { function
41 assertEquals("ok", crash(null));
42 assertEquals("ok", crash(null));
43 %OptimizeFunctionOnNextCall(crash);
45 assertEquals("ok", crash(1));
Dregress-crbug-513602.js11 function crash() { function
15 crash();
16 crash();
22 crash();
26 crash();
Dregress-crbug-349079.js12 function crash() { function
20 crash();
21 crash();
22 %OptimizeFunctionOnNextCall(crash);
23 crash();
Dregress-crbug-351320.js13 function crash() { function
19 crash();
20 %OptimizeFunctionOnNextCall(crash);
21 crash();
Dregress-crbug-349853.js11 function crash() { function
21 crash();
/external/autotest/server/site_tests/logging_KernelCrashServer/
Dcontrol15 This test crashes the client and verifies the kernel crash was collected.
18 - kernel does not support crash dumping
19 - kernel crash dump doesn't appear after crash
20 - crash dump does not appear to be correct
21 - crash report is not sent properly
25 # We have set up our autotest to copy off the crashes in /var/spool/crash
27 # client-side tests and require that the content of /var/spool/crash be
29 # /var/spool/crash entry from the test_loggables so that autotest doesn't
32 if type(log) is purgeable_logdir and log.dir == '/var/spool/crash':
/external/clang/test/Modules/
Dsignal.m1 // REQUIRES: crash-recovery,shell
5 // RUN: not --crash %clang_cc1 -fmodules -fimplicit-module-maps -fmodules-cache-path=%t -I%S/Inputs…
8 // RUN: find %t -name "crash-*.pcm.lock" | count 1
9 // RUN: find %t -name "crash-*.pcm.lock-*" | count 0
11 @import crash;
/external/clang/test/Driver/
Dcrash-report-modules.m8 // RUN: FileCheck --check-prefix=CHECKSRC %s -input-file %t/crash-report-*.m
9 // RUN: FileCheck --check-prefix=CHECKSH %s -input-file %t/crash-report-*.sh
10 // REQUIRES: crash-recovery
15 // FIXME: This XFAIL is cargo-culted from crash-report.c. Do we need it?
36 // CHECKSH: "crash-report-modules-{{[^ ]*}}.m"
37 // CHECKSH: "-ivfsoverlay" "crash-report-modules-{{[^ ]*}}.cache/vfs/vfs.yaml"
/external/clang/test/Index/
Dcrash-recovery-modules.m4 // Parse the file, such that building the module will cause Clang to crash.
7 // CHECK-CRASH: crash-recovery-modules.m:16:9:{16:2-16:14}: fatal error: could not build module 'Cr…
13 // REQUIRES: crash-recovery
19 #pragma clang __debug crash
28 // Check that libclang crash-recovery works; both with a module building crash...
34 // CHECK-LIBCLANG-CRASH: libclang: crash detected during parsing
/external/clang/test/CodeGenObjC/
Dclass-getter-dotsyntax.m4 + (Test *)crash; class
15 Test *crash = Test.crash;
18 + (Test *)crash{ return 0; } class
/external/autotest/client/site_tests/logging_CrashSender/
Dcontrol7 PURPOSE = "Verify crash sender works."
10 - crash log messages are incorrect
11 - crash is sent without user consent
22 Test that crash sender works correctly.
/external/valgrind/none/tests/
Dempty-exe.vgtest1 # Bug 162020: running an empty executable used to crash Valgrind. Note that
2 # the (old) crash message gets filtered out, so it's the presence of the
4 # indicate it ran to completion. If the crash occurs, the .stderr.out file
/external/clang/test/PCH/
Dchain-friend-instantiation.cpp46 struct crash { struct
49 crash(const TClass<std::s> p) in crash() argument
59 crash c(p); in f()
/external/autotest/client/site_tests/logging_UserCrash/
Dcontrol11 - user space crash handling is not running
12 - forced crash does not occur
15 - crash is sent without user consent
/external/clang/test/Analysis/
Dmisc-ps.m62 // Reduced test case from crash in <rdar://problem/6253157>
70 // Reduced test case from crash in PR 2796;
209 // - We just want to test that this doesn't crash the analyzer.
344 // Previously this case would crash.
352 // types. This was previously causing a crash in CastRegion.
382 // get a crash here due to an assertion failure.
442 // This test reproduces a case for a crash when analyzing ClamAV using
443 // RegionStoreManager (the crash doesn't exhibit in BasicStoreManager because
458 // It should not crash.
468 // This previously was a crash in RegionStoreManager.
[all …]
/external/clang/test/CodeGenCXX/
Ddebug-info-globalinit.cpp3 void crash() { in crash() function
9 crash(); in test()
/external/llvm/test/CodeGen/X86/
Dreturn_zeroext_i2.ll2 ; Check that the testcase does not crash
3 define zeroext i2 @crash () {
Dseh-catch-all.ll7 declare void @crash()
12 invoke void @crash()
31 ; CHECK: callq crash
/external/clang/test/Parser/
Dobjc-diag-width.mm3 // Just shouldn't crash. -verify suppresses the crash, so don't use it.
/external/llvm/docs/
DHowToSubmitABug.rst39 More often than not, bugs in the compiler cause it to crash---often due to
46 generator), run the ``clang`` command line as you were when the crash
50 options (which disable the optimizer and code generator), then the crash
58 * Otherwise, you have a code generator crash. Jump ahead to `code
68 command that resulted in the crash, but add the ``-save-temps`` option.
69 The compiler will crash again, but it will leave behind a ``foo.i`` file
95 then it should crash in the same way as clang. If it doesn't crash, please
98 If this does crash, then you should be able to debug this with the following
123 If none of these crash, please follow the instructions for a `front-end
124 bug`_. If one of these do crash, you should be able to reduce this with

12345678910>>...28