Home
last modified time | relevance | path

Searched refs:stacktrace (Results 1 – 25 of 1944) sorted by relevance

12345678910>>...78

/linux/tools/testing/fault-injection/
A Dfailcmd.sh43 --stacktrace-depth=value, --require-start=value, --require-end=value,
88 LONGOPTS=$LONGOPTS,stacktrace-depth:,require-start:,require-end:
158 --stacktrace-depth)
159 echo $2 > $FAULTATTR/stacktrace-depth
/linux/tools/testing/selftests/ftrace/test.d/trigger/
A Dtrigger-stacktrace.tc11 FEATURE=`grep stacktrace events/sched/sched_process_fork/trigger`
19 echo 0 > options/stacktrace
/linux/arch/csky/kernel/
A DMakefile6 obj-y += process.o cpu-probe.o ptrace.o stacktrace.o
12 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux/arch/alpha/lib/
A Dstacktrace.c91 stacktrace(void) in stacktrace() function
94 instr * prologue = (instr *)stacktrace; in stacktrace()
/linux/tools/testing/selftests/ftrace/test.d/ftrace/
A Dfunc-filter-stacktrace.tc7 echo $FUNCTION_FORK:stacktrace >> set_ftrace_filter
/linux/Documentation/livepatch/
A Dreliable-stacktrace.rst16 to identify which functions are live is to use a stacktrace.
18 Existing stacktrace code may not always give an accurate picture of all
21 to provide a *reliable* stacktrace which ensures it never omits any live
28 Architectures must implement one of the reliable stacktrace functions.
33 Principally, the reliable stacktrace function must ensure that either:
45 Secondly, the reliable stacktrace function must be robust to cases where
89 architectures verify that a stacktrace ends at an expected location, e.g.
A Dindex.rst16 reliable-stacktrace
/linux/arch/openrisc/kernel/
A DMakefile13 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux/tools/testing/ktest/examples/bootconfigs/
A Dtracing.bconf3 options = event-fork, sym-addr, stacktrace;
/linux/arch/hexagon/kernel/
A DMakefile18 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux/arch/arm64/kernel/
A D.stacktrace.o.cmd1stacktrace.o := /usr/bin/ccache /home/test/workspace/code/optee_3.16/build/../toolchains/aarch64/b…
3 source_arch/arm64/kernel/stacktrace.o := arch/arm64/kernel/stacktrace.c
5 deps_arch/arm64/kernel/stacktrace.o := \
888 include/linux/stacktrace.h \
1074 arch/arm64/include/asm/stacktrace.h \
1077 arch/arm64/kernel/stacktrace.o: $(deps_arch/arm64/kernel/stacktrace.o)
1079 $(deps_arch/arm64/kernel/stacktrace.o):
A Dbuilt-in.a14 stacktrace.o/
/linux/arch/microblaze/kernel/
A DMakefile26 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux/arch/xtensa/kernel/
A DMakefile9 ptrace.o setup.o signal.o stacktrace.o syscall.o time.o traps.o \
/linux/arch/nds32/kernel/
A DMakefile16 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux/arch/arc/kernel/
A DMakefile7 obj-y += signal.o traps.o sys.o troubleshoot.o stacktrace.o disasm.o
/linux/Documentation/trace/
A Dhistogram.rst557 { stacktrace:
575 { stacktrace:
590 { stacktrace:
602 { stacktrace:
610 { stacktrace:
619 { stacktrace:
630 { stacktrace:
1056 { stacktrace:
1073 { stacktrace:
1091 { stacktrace:
[all …]
A Devents.rst423 - stacktrace
425 This command dumps a stacktrace in the trace buffer whenever the
428 For example, the following trigger dumps a stacktrace every time the
431 # echo 'stacktrace' > \
437 # echo 'stacktrace:5 if bytes_req >= 65536' > \
442 stacktrace[:count]
446 # echo '!stacktrace' > \
449 # echo '!stacktrace:5 if bytes_req >= 65536' > \
455 # echo '!stacktrace:5' > \
458 Note that there can be only one stacktrace trigger per triggering
[all …]
/linux/Documentation/fault-injection/
A Dfault-injection.rst119 stacktrace walking. Failure is injected only if some caller
120 in the walked stacktrace lies within the required range, and
125 - /sys/kernel/debug/fail*/stacktrace-depth:
127 specifies the maximum stacktrace depth walked during search
339 echo 10 > /sys/kernel/debug/$FAILTYPE/stacktrace-depth
/linux/arch/sh/kernel/
A DMakefile38 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux/arch/um/kernel/
A DMakefile25 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux/arch/parisc/kernel/
A DMakefile29 obj-$(CONFIG_STACKTRACE)+= stacktrace.o
/linux/arch/ia64/kernel/
A DMakefile35 obj-$(CONFIG_STACKTRACE) += stacktrace.o
/linux/arch/riscv/kernel/
A DMakefile35 obj-y += stacktrace.o
/linux/arch/s390/kernel/
A DMakefile58 obj-$(CONFIG_STACKTRACE) += stacktrace.o

Completed in 37 milliseconds

12345678910>>...78