| /external/chromium_org/third_party/sqlite/src/test/ |
| D | crash.test | 20 # $Id: crash.test,v 1.27 2008/01/08 15:18:52 drh Exp $
43 # Simple crash test:
45 # crash-1.1: Create a database with a table with two rows.
46 # crash-1.2: Run a 'DELETE FROM abc WHERE a = 1' that crashes during
48 # crash-1.3: Ensure the database is in the same state as after crash-1.1.
49 # crash-1.4: Run a 'DELETE FROM abc WHERE a = 1' that crashes during
51 # crash-1.5: Ensure the database is in the same state as after crash-1.1.
52 # crash-1.6: Run a 'DELETE FROM abc WHERE a = 1' that crashes during
54 # crash-1.7: Ensure the database is in the same state as after crash-1.1.
61 do_test crash-1.1 {
[all …]
|
| D | crash3.test | 41 # This block tests crash-recovery when the IOCAP_ATOMIC flags is set.
49 # Then execute the SQL statement, scheduling a crash for part-way through
51 # the journal file is not required - meaning no crash occurs).
53 # After the crash (or absence of a crash), open the database and
61 # with the crash scheduled for midway through the first journal sync (if
62 # any), and five times with the crash midway through the database sync.
|
| /external/chromium_org/v8/test/mjsunit/regress/ |
| D | regress-crbug-134055.js | 30 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);
|
| D | post-increment-close-context.js | 31 function crash() { function
34 assertFalse(crash());
36 %OptimizeFunctionOnNextCall(crash);
37 assertFalse(crash());
39 assertTrue(crash());
41 assertFalse(crash());
|
| D | regress-crbug-196583.js | 42 function crash(obj) { function
47 crash(a);
48 crash(b);
49 crash(c);
51 %OptimizeFunctionOnNextCall(crash);
52 assertEquals(1, crash(a));
|
| D | regress-crbug-285355.js | 36 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)));
|
| D | regress-crbug-258519.js | 35 function crash(x) { function
41 assertEquals("ok", crash(null));
42 assertEquals("ok", crash(null));
43 %OptimizeFunctionOnNextCall(crash);
45 assertEquals("ok", crash(1));
|
| D | regress-crbug-349079.js | 12 function crash() { function
20 crash();
21 crash();
22 %OptimizeFunctionOnNextCall(crash);
23 crash();
|
| /external/chromium_org/ppapi/native_client/tests/breakpad_crash_test/ |
| D | nacl.scons | 13 # We are also checking that crash dumping does not work
28 # produce crash dumps via Breakpad.
32 browser_flags=['--crash-test'], # Tell the browser process to crash.
42 # Additionally, the test affects crash stats on Mac because it uploads
43 # crash dumps on the bots for the Chrome official build.
51 # This crash in trusted code should produce a crash dump.
71 # This tests a crash that occurs inside a syscall handler.
72 # Ultimately this should be recognised as a crash caused by untrusted code.
90 # Crashes in untrusted code should not produce crash dumps.
|
| /external/clang/test/CodeGenObjC/ |
| D | class-getter-dotsyntax.m | 4 + (Test *)crash; class
15 Test *crash = Test.crash;
18 + (Test *)crash{ return 0; } class
|
| /external/clang/test/Index/ |
| D | crash-recovery-modules.m | 4 // 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/chromium/chrome/browser/resources/ |
| D | crashes.js | 36 var crash = crashes[i];
41 crash['id']);
45 crash['time']);
62 crash['id'];
|
| /external/chromium_org/chrome/browser/resources/ |
| D | crashes.js | 34 var crash = crashes[i];
39 crash['id']);
43 crash['time']);
65 'report_id:' + crash.id
|
| /external/chromium_org/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/ |
| D | test.py | 48 self.crash = False
86 def add_reftest(self, name, reference_name, same_image, crash=False): argument
87 self.add(name, actual_checksum='xxx', actual_image='XXX', is_reftest=True, crash=crash)
113 tests.add('failures/expected/crash.html', crash=True)
161 tests.add('failures/unexpected/crash.html', crash=True)
162 tests.add('failures/unexpected/crash-with-stderr.html', crash=True,
217 …rash-reftest.html', 'failures/unexpected/crash-reftest-expected.html', same_image=True, crash=True)
593 crash = test.crash
607 crash = True
613 crash = True
[all …]
|
| /external/valgrind/main/none/tests/ |
| D | empty-exe.vgtest | 1 # 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/ |
| D | chain-friend-instantiation.cpp | 46 struct crash { struct
49 crash(const TClass<std::s> p) in crash() function
59 crash c(p); in f()
|
| /external/clang/test/CodeGenCXX/ |
| D | debug-info-globalinit.cpp | 3 void crash() { in crash() function
9 crash(); in test()
|
| /external/chromium_org/components/breakpad/app/ |
| D | breakpad_mac.mm | 36 // IMPORTANT: On OS X, the key/value pairs are sent to the crash server
73 // fatal crash at the same time, this should work.
93 // Rather than including the code to force the crash here, allow the
137 // Most interesting operations are not safe in a signal handler, just crash.
153 // Check whether crash reporting should be enabled. If enterprise
154 // configuration management controls crash reporting, it takes precedence.
155 // Otherwise, check whether the user has consented to stats and crash
169 // Controlled by the user. The crash reporter may be enabled by
227 // Initialize the scoped crash key system.
250 // Register a signal handler to crash in a way breakpad will
[all …]
|
| /external/chromium_org/chrome/browser/ui/webui/ |
| D | crashes_ui.cc | 140 DictionaryValue* crash = new DictionaryValue(); in UpdateUI() local
141 crash->SetString("id", i->id); in UpdateUI()
142 crash->SetString("time", base::TimeFormatFriendlyDateAndTime(i->time)); in UpdateUI()
143 crash_list.Append(crash); in UpdateUI()
|
| /external/clang/test/Parser/ |
| D | objc-diag-width.mm | 3 // Just shouldn't crash. -verify suppresses the crash, so don't use it.
|
| /external/chromium/chrome/browser/ui/webui/ |
| D | crashes_ui.cc | 175 DictionaryValue* crash = new DictionaryValue(); in UpdateUI() local
176 crash->SetString("id", i->crash_id); in UpdateUI()
177 crash->SetString("time", in UpdateUI()
179 crash_list.Append(crash); in UpdateUI()
|
| /external/chromium_org/third_party/WebKit/ManualTests/ |
| D | .gitattributes | 4 empty-script-crash.html -crlf
5 remove-form-node-with-radio-buttons-crash.html -crlf
|
| /external/pixman/test/ |
| D | Makefile.sources | 16 scaling-crash-test \
18 gradient-crash-test \
|
| /external/clang/test/Analysis/ |
| D | misc-ps.m | 62 // Reduced test case from crash in <rdar://problem/6253157>
70 // Reduced test case from crash in PR 2796;
222 // - We just want to test that this doesn't crash the analyzer.
357 // Previously this case would crash.
365 // types. This was previously causing a crash in CastRegion.
395 // get a crash here due to an assertion failure.
455 // This test reproduces a case for a crash when analyzing ClamAV using
456 // RegionStoreManager (the crash doesn't exhibit in BasicStoreManager because
471 // It should not crash.
481 // This previously was a crash in RegionStoreManager.
[all …]
|
| /external/llvm/docs/ |
| D | HowToSubmitABug.rst | 39 More often than not, bugs in the compiler cause it to crash---often due to
46 generator), run the ``llvm-gcc`` 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 llvm-gcc. 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
|