| /external/cldr/tools/java/org/unicode/cldr/util/ |
| D | StackTracker.java | 36 private Hashtable<Object, String> stacks = new Hashtable<>(); field in StackTracker
45 stacks.put(o, stack); in add()
54 stacks.remove(o); in remove()
78 if (stacks.isEmpty()) { in toString()
85 for (Map.Entry<Object, String> e : stacks.entrySet()) { in toString()
86 sb.append("Held Obj #" + (++n) + "/" + stacks.size() + ": " + e.getKey() + "\n"); in toString()
97 stacks.clear(); in clear()
124 return stacks.isEmpty(); in isEmpty()
132 return stacks.keySet().iterator(); in iterator()
|
| /external/bcc/tools/old/ |
| D | memleak.py | 245 stacks = {}
253 if stack in stacks:
254 stacks[stack] = (stacks[stack][0] + 1,
255 stacks[stack][1] + info.size)
257 stacks[stack] = (1, info.size)
261 to_show = sorted(stacks.items(), key=lambda s: s[1][1])[-top_stacks:]
|
| D | profile_example.txt | 161 Lets add delimiters between the user and kernel stacks, using -d:
270 frequency counting and only printing unique stacks? We are, but in terms of
271 the raw addresses, not the symbols. See the 1st column: those stacks are
574 You can also restrict profiling to just kernel stacks (-K) or user stacks (-U).
575 For example, just user stacks:
736 If this doesn't work on your architecture (and your kernel stacks are a
762 -U, --user-stacks-only
763 show stacks from user space only (no kernel space
764 stacks)
765 -K, --kernel-stacks-only
[all …]
|
| /external/tensorflow/tensorflow/python/autograph/core/ |
| D | ag_ctx.py | 27 stacks = threading.local() variable
31 if not hasattr(stacks, 'control_status'):
32 stacks.control_status = [_default_control_status_ctx()]
33 return stacks.control_status
|
| /external/compiler-rt/lib/tsan/rtl/ |
| D | tsan_report.cc | 56 : stacks(MBlockReportStack) in ReportDesc()
259 if (rep->stacks.Size()) in ChooseSummaryStack()
260 return rep->stacks[0]; in ChooseSummaryStack()
306 rep->stacks.Size()); in PrintReport()
316 PrintStack(rep->stacks[2*i]); in PrintReport()
320 PrintStack(rep->stacks[2*i+1]); in PrintReport()
322 PrintStack(rep->stacks[i]); in PrintReport()
329 for (uptr i = 0; i < rep->stacks.Size(); i++) { in PrintReport()
332 PrintStack(rep->stacks[i]); in PrintReport()
444 PrintStack(rep->stacks[2*i]); in PrintReport()
[all …]
|
| D | tsan_debugging.cc | 72 *stack_count = rep->stacks.Size(); in __tsan_get_report_data()
86 CHECK_LT(idx, rep->stacks.Size()); in __tsan_get_report_stack()
87 ReportStack *stack = rep->stacks[idx]; in __tsan_get_report_stack()
|
| D | tsan_platform_linux.cc | 117 StackDepotStats *stacks = StackDepotGetStats(); in WriteMemoryProfile() local
124 stacks->allocated >> 20, stacks->n_uniq_ids, in WriteMemoryProfile()
|
| /external/gemmlowp/profiling/ |
| D | profiler.h | 241 explicit ProfileTreeView(const std::vector<ProfilingStack>& stacks) { in ProfileTreeView() argument
242 for (auto stack : stacks) { in ProfileTreeView()
328 std::vector<ProfilingStack> stacks; in ProfilerThreadFunc() local
337 stacks.push_back(s); in ProfilerThreadFunc()
343 ProfileTreeView(stacks).Print(); in ProfilerThreadFunc()
|
| /external/bcc/tools/ |
| D | memleak_example.txt | 5 collects call stacks for each allocation. memleak can then print a summary
6 of which call stacks performed allocations that weren't subsequently freed.
11 [11:16:33] Top 2 stacks with outstanding allocations:
16 [11:16:34] Top 2 stacks with outstanding allocations:
37 [11:16:33] Top 2 stacks with outstanding allocations:
46 [11:16:34] Top 2 stacks with outstanding allocations:
130 [11:16:33] Top 2 stacks with outstanding allocations:
135 [11:16:38] Top 2 stacks with outstanding allocations:
140 [11:16:43] Top 2 stacks with outstanding allocations:
173 stacks
[all …]
|
| D | stackcount_example.txt | 81 walkers. Similar broken stacks will be seen by other profilers and debuggers
93 Now adding the -d option to delimit kernel and user stacks:
179 A "--" is printed between the kernel and user stacks.
290 some Java stacks where user-level has been walked correctly (even includes a
365 Watch what happens if I filter on kernel stacks only (-K) for ip_output():
392 Here is just the user stacks, fetched during the kernel function ip_output():
438 Kernel stacks are absent as this didn't enter kernel code.
770 kernel stacks only (-K) with offsets (-s):
866 -P, --perpid display stacks separately for each process
867 -K, --kernel-stacks-only
[all …]
|
| D | offcputime_example.txt | 10 Here is some example output. The -K option was used to only match kernel stacks.
658 A -f option will emit output using the "folded stacks" format, which can be
740 -U, --user-stacks-only
741 show stacks from user space only (no kernel space
742 stacks)
743 -K, --kernel-stacks-only
744 show stacks from kernel space only (no user space
745 stacks)
746 -d, --delimited insert delimiter between kernel/user stacks
770 ./offcputime -U # only show user space stacks (no kernel)
[all …]
|
| D | offwaketime_example.txt | 10 The combined stacks, task names, and total time is summarized in kernel context
173 The number beneath the stacks is the total time spent from the blocking event
179 show the stacks in "folded stacks" format. Eg:
326 -U, --user-stacks-only
327 show stacks from user space only (no kernel space
328 stacks)
329 -K, --kernel-stacks-only
330 show stacks from kernel space only (no user space
331 stacks)
332 -d, --delimited insert delimiter between kernel/user stacks
[all …]
|
| D | profile_example.txt | 160 Lets add delimiters between the user and kernel stacks, using -d:
269 frequency counting and only printing unique stacks? We are, but in terms of
270 the raw addresses, not the symbols. See the 1st column: those stacks are
573 You can also restrict profiling to just kernel stacks (-K) or user stacks (-U).
574 For example, just user stacks:
754 -U, --user-stacks-only
755 show stacks from user space only (no kernel space
756 stacks)
757 -K, --kernel-stacks-only
758 show stacks from kernel space only (no user space
[all …]
|
| D | capable_example.txt | 87 ./capable -K # add kernel stacks to trace
88 ./capable -U # add user-space stacks to trace
|
| /external/llvm-project/compiler-rt/lib/tsan/rtl/ |
| D | tsan_report.cpp | 50 , stacks() in ReportDesc()
287 if (rep->stacks.Size()) in ChooseSummaryStack()
288 return rep->stacks[0]; in ChooseSummaryStack()
334 rep->stacks.Size()); in PrintReport()
344 PrintStack(rep->stacks[2*i]); in PrintReport()
348 PrintStack(rep->stacks[2*i+1]); in PrintReport()
350 PrintStack(rep->stacks[i]); in PrintReport()
357 for (uptr i = 0; i < rep->stacks.Size(); i++) { in PrintReport()
360 PrintStack(rep->stacks[i]); in PrintReport()
475 PrintStack(rep->stacks[2*i]); in PrintReport()
[all …]
|
| D | tsan_platform_mac.cpp | 162 StackDepotStats *stacks = StackDepotGetStats(); in WriteMemoryProfile() local
187 stacks->n_uniq_ids, stacks->allocated / 1024, in WriteMemoryProfile()
|
| D | tsan_debugging.cpp | 80 *stack_count = rep->stacks.Size(); in __tsan_get_report_data()
101 CHECK_LT(idx, rep->stacks.Size()); in __tsan_get_report_stack()
102 ReportStack *stack = rep->stacks[idx]; in __tsan_get_report_stack()
|
| /external/tensorflow/tensorflow/python/util/ |
| D | tf_stack_test.py | 31 stacks = tf_stack.extract_stack(), traceback.extract_stack()
33 traceback.format_list(stacks[0]), traceback.format_list(stacks[1]))
|
| /external/bcc/examples/cpp/ |
| D | TCPSendStack.cc | 89 auto stacks = bpf.get_stack_table("stack_traces"); in main() local
98 auto syms = stacks.get_stack_symbol(it.first.kernel_stack, -1); in main()
111 auto syms = stacks.get_stack_symbol(it.first.user_stack, it.first.pid); in main()
|
| /external/llvm-project/llvm/docs/ |
| D | XRayExample.rst | 204 The way to use the command is to output the top stacks by call count and time spent.
226 In the default mode, identical stacks on different threads are independently
228 stacks fill your list of top calls.
231 ``-per-thread-stacks`` flags. ``-per-thread-stacks`` treats the thread id as an
233 identical stacks from all threads.
246 - ``-all-stacks`` - Emits all of the stacks.
255 …xray-log.llc.5rqxkU -instr_map ./bin/llc -stack-format=flame -aggregation-type=time -all-stacks | \
258 If you open the svg in a browser, mouse events allow exploring the call stacks.
346 - Collecting function call stacks and how often they're encountered in the
|
| /external/llvm-project/compiler-rt/lib/lsan/ |
| D | lsan_common_fuchsia.cpp | 79 auto stacks = +[](void *chunk, size_t size, void *data) { in LockStuffAndStopTheWorld() local
132 flags()->use_stacks ? stacks : nullptr, in LockStuffAndStopTheWorld()
|
| /external/bcc/src/cc/frontends/p4/compiler/ |
| D | ebpfProgram.py | 64 self.stacks = [] # header stack instances EbpfHeaderStack
94 self.stacks.append(stack)
285 for h in self.stacks:
379 for h in self.stacks:
388 for h in self.stacks:
|
| /external/arm-trusted-firmware/include/plat/arm/common/ |
| D | arm_reclaim_init.ld.S | 29 stacks (NOLOAD) : { \
|
| /external/llvm-project/llvm/tools/llvm-xray/ |
| D | CMakeLists.txt | 20 xray-stacks.cpp
|
| /external/ruy/ruy/profiler/ |
| D | README.md | 1 # A minimalistic profiler sampling pseudo-stacks
8 Contrary to most typical profilers, what it samples is not real call stacks, but
9 "pseudo-stacks" which are just simple data structures constructed from within
149 stacks, from just symbol information generated by the toolchain.
|