Lines Matching refs:to

7 This documentation describes how to enable this feature on Android N or later
33 Before, a realloc from one size to a smaller size would not update the
34 backtrace related to the allocation. Starting in P, every single realloc
49 to find memory corruption occuring to a region before the original allocation.
51 When the allocation is freed, the guard is checked to verify it has not been
61 on 64 bit systems to make sure that the allocation returned is aligned
64 This option adds a special header to all allocations that contains the guard
75 to find memory corruption occuring to a region after the original allocation.
77 When the allocation is freed, the guard is checked to verify it has not been
84 This option adds a special header to all allocations that contains
108 If MAX\_FRAMES is present, it indicates the maximum number of frames to
110 this can be set to is 256.
112 Before P, this option adds a special header to all allocations that contains
116 As of P, this option will also enable dumping backtrace heap data to a
119 that dumped when running am dumpheap -n. The default is to dump this data
120 to the file /data/local/tmp/backtrace\_heap.**PID**.txt. This is useful when
135 If MAX\_FRAMES is present, it indicates the maximum number of frames to
137 this can be set to is 256.
139 Before P, this option adds a special header to all allocations that contains
145 dump heap data to be dumped to a file when the program exits. If the backtrace
146 option has not been enabled, this does nothing. The default is to dump this
147 to the file named /data/local/tmp/backtrace\_heap.**PID**.exit.txt.
170 filled with the value 0xeb. When doing a realloc to a larger size, the bytes
171 above the original usable size will be set to 0xeb.
173 If MAX\_FILLED\_BYTES is present, it will only fill up to the specified number
174 of bytes in the allocation. The default is to fill the entire allocation.
179 If MAX\_FILLED\_BYTES is present, it will only fill up to the specified number
180 of bytes in the allocation. The default is to fill the entire allocation.
185 If MAX\_FILLED\_BYTES is present, it will only fill up to the specified number
186 of bytes in the allocation. The default is to fill the entire allocation.
189 Add an extra amount to allocate for every allocation.
191 If XX is present, it is the number of bytes to expand the allocation by.
195 When a pointer is freed, do not free the memory right away, but add it to
196 a list of freed allocations. In addition to being added to the list, the
202 option. It can also be completely disabled by setting the option to zero.
206 checked to make sure that none of the contents have been modified since
211 in the list. The default is to record 100 freed allocations, the max
212 allocations to record is 16384.
214 Before P, this option adds a special header to all allocations that contains
238 backtrace frames to capture when an allocation is freed.
240 If MAX\_FRAMES is present, it indicates the number of frames to capture.
241 If the value is set to zero, then no backtrace will be captured when the
242 allocation is freed. The default is to record 16 frames, the max number of
243 frames to to record is 256.
247 allocations will be dumped to the log. If the backtrace option was enabled,
252 Before P, this option adds a special header to all allocations that contains
273 to a file when the signal SIGRTMAX - 18 (which is 46 on most Android devices)
280 can be set to is 50,000,000.
282 Once the signal is received, and the current records are written to the
284 the data is being dumped to the file are ignored.
291 to the file. However, when a thread completes, a special entry is added to
378 Track all live allocations to determine if a pointer is used that does not
379 exist. This option is a lightweight way to verify that all
412 slow down process start up. However, if you want to re-enable these messages,
417 …09-10 01:03:50.070   557   557 I malloc_debug: /system/bin/audioserver: Run: 'kill -47 557' to dum…
436 This indicates that code is attempting to free an already freed pointer. The
517 The map data is simply the output of /proc/PID/maps. This data can be used to
528 NUM\_ALLOCATIONS to an incorrect value. For heap dump v1.0, the
550 be added to every backtrace line. The line will be:
558 RELATIVE\_TO\_MAP\_PC is the hexadecimal value of the relative pc to the map.
576 There is a tool to visualize this data,
610 The outer layer of quoting is for the shell on the host, to ensure that the
611 inner layer of quoting is sent to the device, to make 'backtrace guard'
636 It is possible to use the backtrace\_enable\_on\_signal option as well,
644 for the best way to use malloc debug in Android O or later on non-rooted
652 If you need to enable multiple options using this method, then you can set
657 For example, to enable malloc debug for the google search box (Android O or later):
662 If you are setting multiple options and the app does not appear to start
676 of 32. This meant that to create a wrap property with the name of the app, it
677 was necessary to truncate the name to fit. On O, property names can be
678 an order of magnitude larger, so there should be no need to truncate the name
691 For backtraces from your app to be useful, you'll want to keep the
693 way you'll see the location of the leak directly without having to use
701 In order for the script to properly symbolize the stacks in the file,
708 …python development/scripts/native_heapdump_viewer.py --symbols /some/path/to/symbols/ heap.txt > h…
712 is at `/data/app/.../lib/arm/libx.so` on the device, it will need to be at
713 `/some/path/to/symbols/data/app/.../lib/arm/libx.so` locally given the
714 command line above. That is: you need to mirror the directory structure