| /openbsd/gnu/llvm/llvm/utils/lit/tests/Inputs/shtest-not/ |
| H A D | not-calls-external.txt | 13 # Simple uses of 'not --crash'
15 # RUN: not not --crash %{python} pass.py
16 # RUN: not not --crash %{python} fail.py
17 # RUN: not not --crash not %{python} pass.py
18 # RUN: not not --crash not %{python} fail.py
48 # Various patterns of 'not', 'not --crash', and 'env'
50 # RUN: not env FOO=1 BAR=1 env FOO=2 BAR=2 not --crash %{python} pass.py \
53 # RUN: not env FOO=1 BAR=1 not --crash not %{python} pass.py \
56 # RUN: not not --crash env -u BAR not env -u FOO BAR=1 %{python} pass.py \
|
| H A D | not-calls-diff-with-crash.txt | 1 # Lit's diff is out-of-process, so check that "not --crash diff" fails because
2 # diff doesn't crash rather than because "not --crash diff" isn't supported.
6 # RUN: not --crash diff -u %t.foo %t.bar
|
| H A D | not-args-last-is-crash.txt | 1 # RUN: not --crash
|
| H A D | not-calls-colon.txt | 3 # RUN: not --crash :
|
| H A D | not-calls-rm.txt | 2 # RUN: not --crash rm foobar
|
| H A D | not-calls-mkdir.txt | 2 # RUN: not --crash mkdir foobar
|
| H A D | not-calls-export.txt | 3 # RUN: not --crash export BAZ=3
|
| H A D | not-calls-cd.txt | 3 # RUN: not --crash cd foobar
|
| /openbsd/gnu/llvm/llvm/docs/ |
| H A D | HowToSubmitABug.rst | 52 the crash is in the front-end. Jump ahead to :ref:`front-end bugs
53 <frontend-crash>`.
57 :ref:`middle-end bugs <middleend-crash>`.
60 generator bugs <backend-crash>`.
62 .. _frontend-crash:
83 compiler crash.
87 .. _middleend-crash:
103 bug <frontend-crash>`.
123 ``llvm-reduce`` is still fairly immature and may crash.
129 .. _backend-crash:
[all …]
|
| H A D | Bugpoint.rst | 16 optimization (or combination of optimizations) that causes the crash, and reduce
17 the file down to a small example which triggers the crash.
41 program. If any of the passes crash, or if they produce malformed output (which
42 causes the verifier to abort), ``bugpoint`` starts the `crash debugger`_.
48 selected code generator crashes, ``bugpoint`` starts the `crash debugger`_ on
77 failure. At the end, ``bugpoint`` should tell you what passes crash, give you a
124 * In the `crash debugger`_, ``bugpoint`` does not distinguish different crashes
125 during reduction. Thus, if new crash or miscompilation happens, ``bugpoint``
126 will continue with the new crash instead. If you would like to stick to
127 particular crash, you should write check scripts to validate the error
|
| /openbsd/gnu/llvm/lldb/docs/use/ |
| H A D | symbolication.rst | 10 used to symbolicate your crash logs and can often provide more information than
93 When symbolicating your crash logs, it can be tedious if you always have to
143 Lets say we have a Darwin crash log that contains the following images:
245 crash logs have register information for your threads.
252 added in the darwin crash log example above:
302 it from text that might have been extracted from a crash log file.
340 in the lldb.utils.symbolication to symbolicate the crash logs.
343 interpreter so that you can use it to parse and symbolicate macOS crash
350 (lldb) crashlog /tmp/crash.log
363 disassemble the location of the crash for the first frame of the crashed
[all …]
|
| /openbsd/gnu/llvm/clang/tools/scan-build-py/lib/libscanbuild/ |
| H A D | report.py | 219 crashes = (pretty(crash) for crash in read_crashes(output_dir))
512 def predicate(crash): argument
515 encode_value(crash, 'source', lambda x: escape(chop(prefix, x)))
516 encode_value(crash, 'problem', escape)
517 encode_value(crash, 'file', lambda x: escape(chop(output_dir, x)))
518 encode_value(crash, 'info', lambda x: escape(chop(output_dir, x)))
519 encode_value(crash, 'stderr', lambda x: escape(chop(output_dir, x)))
520 return crash
|
| /openbsd/usr.bin/rpcgen/ |
| H A D | rpc_main.c | 247 crash(); in open_output()
253 crash(); in open_output()
288 crash(); in find_cpp()
295 crash(); in find_cpp()
334 crash(); in open_input()
444 crash(); in generate_guard()
803 crash();
817 crash();
838 crash();
848 crash();
|
| H A D | rpc_util.c | 269 crash();
277 crash() in crash() function
295 crash();
|
| /openbsd/gnu/usr.bin/gcc/gcc/testsuite/g++.old-deja/g++.mike/ |
| H A D | p9732a.C | 14 int crash(const value* capt, value* jet) { in crash() function
30 return crash (&capt, &jet); in distance()
|
| H A D | eh2.C | 47 void crash(Vector& v ) { in crash() function
52 crash( v ); in do_something()
|
| H A D | net13.C | 7 struct crash { struct
|
| /openbsd/games/worm/ |
| H A D | worm.c | 72 __dead void crash(void);
325 crash(); in process()
328 crash(); in process()
358 crash(); in process()
388 crash(void) in crash() function
|
| /openbsd/regress/usr.bin/lastcomm/ |
| H A D | Makefile | 23 PROGS= crash trapstack callstack syscallwx unveil
101 run-trap: crash
103 cp -f crash regress-trap
|
| /openbsd/gnu/llvm/lldb/docs/resources/ |
| H A D | fuzzing.rst | 52 …ll also create directories that will store any inputs that caused LLDB to crash, timeout or run ou…
65 …crash, timeout or run out of memory, the input is saved to a file in the build directory. When run…
67 …your build directory. The input files will have the name ``<fuzzer name>-<crash/timeout/oom>-<hash…
|
| /openbsd/gnu/llvm/compiler-rt/lib/gwp_asan/ |
| H A D | options.inc | 56 "crash. Only one crash per sampled allocation will ever be recorded, and "
57 "if a sampled allocation does actually cause a crash, it'll permanently "
|
| /openbsd/regress/usr.sbin/btrace/ |
| H A D | read-map-after-clear.ok | 1 => Print after clear should not crash 0:
|
| H A D | read-map-after-clear.bt | 5 printf("=> Print after clear should not crash %d:\n", @map);
|
| /openbsd/gnu/usr.bin/gcc/gcc/testsuite/g++.old-deja/g++.pt/ |
| H A D | crash42.C | 10 void crash() in crash() function
|
| /openbsd/gnu/llvm/llvm/utils/lit/tests/Inputs/googletest-crash/ |
| H A D | lit.cfg | 2 config.name = 'googletest-crash'
|