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.
165 that only allocations of a size greater than or equal to
168 equal to backtrace\_min\_size and less than or equal to
174 to only get backtraces for sizes of allocations listed as being leaked.
178 that only allocations of a size less than or equal to
181 equal to backtrace\_min\_size and less than or equal to
187 to only get backtraces for sizes of allocations listed as being leaked.
196 to only get backtraces for sizes of allocations listed as being leaked.
204 As of U, add shorter aliases for backtrace related options to avoid property length restrictions.
220 Android devices). The best way to see the exact signal being used is to
223 Run: 'kill -48 <PID>' to check for unreachable memory.
228 If a process is not doing any allocations, it can be forced to trigger when
234 might be necessary to run:
242 filled with the value 0xeb. When doing a realloc to a larger size, the bytes
243 above the original usable size will be set to 0xeb.
245 If MAX\_FILLED\_BYTES is present, it will only fill up to the specified number
246 of bytes in the allocation. The default is to fill the entire allocation.
251 If MAX\_FILLED\_BYTES is present, it will only fill up to the specified number
252 of bytes in the allocation. The default is to fill the entire allocation.
257 If MAX\_FILLED\_BYTES is present, it will only fill up to the specified number
258 of bytes in the allocation. The default is to fill the entire allocation.
261 Add an extra amount to allocate for every allocation.
263 If XX is present, it is the number of bytes to expand the allocation by.
267 When a pointer is freed, do not free the memory right away, but add it to
268 a list of freed allocations. In addition to being added to the list, the
274 option. It can also be completely disabled by setting the option to zero.
278 checked to make sure that none of the contents have been modified since
283 in the list. The default is to record 100 freed allocations, the max
284 allocations to record is 16384.
286 Before P, this option adds a special header to all allocations that contains
310 backtrace frames to capture when an allocation is freed.
312 If MAX\_FRAMES is present, it indicates the number of frames to capture.
313 If the value is set to zero, then no backtrace will be captured when the
314 allocation is freed. The default is to record 16 frames, the max number of
315 frames to to record is 256.
319 allocations will be dumped to the log. If the backtrace option was enabled,
324 Before P, this option adds a special header to all allocations that contains
344 As of Android V, this option will trigger a call to:
355 to a file when the signal SIGRTMAX - 18 (which is 46 on Android devices)
362 can be set to is 50,000,000.
364 Once the signal is received, and the current records are written to the
366 the data is being dumped to the file are ignored.
373 to the file. However, when a thread completes, a special entry is added to
460 Track all live allocations to determine if a pointer is used that does not
461 exist. This option is a lightweight way to verify that all
494 slow down process start up. However, if you want to re-enable these messages,
499 …09-10 01:03:50.070 557 557 I malloc_debug: /system/bin/audioserver: Run: 'kill -47 557' to dum…
518 This indicates that code is attempting to free an already freed pointer. The
599 The map data is simply the output of /proc/PID/maps. This data can be used to
610 NUM\_ALLOCATIONS to an incorrect value. For heap dump v1.0, the
632 be added to every backtrace line. The line will be:
640 RELATIVE\_TO\_MAP\_PC is the hexadecimal value of the relative pc to the map.
689 The outer layer of quoting is for the shell on the host, to ensure that the
690 inner layer of quoting is sent to the device, to make 'backtrace guard'
715 It is possible to use the backtrace\_enable\_on\_signal option as well,
723 for the best way to use malloc debug in Android O or later on non-rooted
726 **NOTE**: Android 12 introduced a bug that can cause the wrap.\<APP\> property to
738 If you need to enable multiple options using this method, then you can set
743 For example, to enable malloc debug for the google search box (Android O or later):
748 If you are setting multiple options and the app does not appear to start
762 of 32. This meant that to create a wrap property with the name of the app, it
763 was necessary to truncate the name to fit. On O, property names can be
764 an order of magnitude larger, so there should be no need to truncate the name
777 For backtraces from your app to be useful, you'll want to keep the
779 way you'll see the location of the leak directly without having to use