Lines Matching refs:this

7 This documentation describes how to enable this feature on Android N or later
50 On first allocation, this front guard is written with a specific pattern (0xaa).
76 On first allocation, this rear guard is written with a specific pattern (0xbb).
102 system runs too slowly with this option enabled, decreasing the maximum number
110 this can be set to is 256.
112 Before P, this option adds a special header to all allocations that contains
113 the backtrace and information about the original allocation. After that, this
116 As of P, this option will also enable dumping backtrace heap data to a
118 Android devices). The format of this dumped data is the same format as
119 that dumped when running am dumpheap -n. The default is to dump this data
130 SIGRTMAX - 19 (which is 45 on most Android devices). When this
132 is received. If both this option and the backtrace option are set, then
137 this can be set to is 256.
139 Before P, this option adds a special header to all allocations that contains
140 the backtrace and information about the original allocation. After that, this
144 As of P, when the backtrace option has been enabled, this causes the backtrace
146 option has not been enabled, this does nothing. The default is to dump this
153 As of P, when one of the backtrace options has been enabled, this sets the
159 When this value is changed from the default, then the filename chosen
199 separate from the backtrace option, and happens automatically if this
201 but this value can be changed using the free\_track\_backtrace\_num\_frames
203 See the full description of this option below.
214 Before P, this option adds a special header to all allocations that contains
215 the backtrace and information about the original allocation. After that, this
252 Before P, this option adds a special header to all allocations that contains
253 the backtrace and information about the original allocation. After that, this
279 not recorded. The default value is 8,000,000 and the maximum value this
292 the file indicating this.
392 with a bad pointer. Only three functions do this checking: free,
406 in Android P and older, enabling malloc debug would result in this message
411 In android Q, this message will not be displayed because these info messages
440 For example, this message:
468 The data has this header:
480 Following this header are two different sections, the first section is the
483 The allocation record data has this format:
487 ZYGOTE\_CHILD\_ALLOC is either 0 or 1. 0 means this was allocated by the
488 zygote process or in a process not spawned from the zygote. 1 means this
492 NUM\_ALLOCATIONS is the number of allocations that have this size and have the
503 with this backtrace/size and a backtrace of 0xa230, 0xb500.
532 Android Q introduces v1.2 of the heap dump. The new header looks like this:
557 no valid map name, this will be empty.
559 FUNCTION\_NAME the name of the function for this pc. If there is no valid
562 the FUNCTION\_NAME is empty, then this value will always be zero.
564 An example of this new format:
569 In this example, the first backtrace frame has a pc of 0xa2a0 and is in the
576 There is a tool to visualize this data,
628 Any process spawned from this shell will run with malloc debug enabled
652 If you need to enable multiple options using this method, then you can set
663 properly, check the logcat looking for this message
668 If you do not see this message, then the wrap property was not set correctly.
685 Without also enabling malloc debug, this command will only tell