Lines Matching refs:in
30 Any errors detected by the library are reported in the log.
32 NOTE: There is a small behavioral change beginning in P for realloc.
34 backtrace related to the allocation. Starting in P, every single realloc
42 individually, or in a group of other options. Every single option can be
53 in the log indicating what bytes changed.
58 If SIZE\_BYTES is present, it indicates the number of bytes in the guard.
79 in the log indicating what bytes changed.
81 If SIZE\_BYTES is present, it indicates the number of bytes in the guard.
96 If SIZE\_BYTES is present, it indicates the number of bytes in both guards.
109 capture in a backtrace. The default is 16 frames, the maximumum value
136 capture in a backtrace. The default is 16 frames, the maximumum value
169 Any allocation routine, other than calloc, will result in the allocation being
174 of bytes in the allocation. The default is to fill the entire allocation.
180 of bytes in the allocation. The default is to fill the entire allocation.
186 of bytes in the allocation. The default is to fill the entire allocation.
211 in the list. The default is to record 100 freed allocations, the max
232 in the log:
256 Example leak error found in the log:
288 The allocation data is written in a human readable format. Every line begins
302 Below is how each type of allocation/free call ends up in the file dump.
406 in Android P and older, enabling malloc debug would result in this message
407 in the log:
421 There are a few other error messages that might appear in the log.
437 name in parenthesis indicates that the application called the function
459 As with the other error message, the function in parenthesis is the
488 zygote process or in a process not spawned from the zygote. 1 means this
518 decode the frames in the backtraces.
527 value is always accurate in v1.1. A previous version of malloc debug set
554 For each backtrace pc, there will be one element in braces.
556 MAP\_NAME is the name of the map in which the backtrace pc exists. If there is
569 In this example, the first backtrace frame has a pc of 0xa2a0 and is in the
571 and it is in the function abort + 0x24.
572 The second backtrace frame has a pc of 0xb510 and is in the map named
574 it is in an unknown function.
609 Note: The two levels of quoting in the adb shell command is necessary.
644 for the best way to use malloc debug in Android O or later on non-rooted
692 symbols in your app's shared libraries rather than stripping them. That
701 In order for the script to properly symbolize the stacks in the file,
710 At the moment, the script will look for symbols in the given directory,
715 for the app in the symbols directory.