oh, and if you're on a recent AOSP build, you might want to try
cherrypicking
https://android-review.googlesource.com/c/platform/frameworks/base/+/1978990
--- the `wrap.` system properties are a bit broken atm. (the wrap.sh stuff
for apps works fine though.)

On Tue, Feb 15, 2022 at 12:40 PM enh <[email protected]> wrote:

> you did replace `[process]` with your actual process name, right?
>
> On Tue, Feb 15, 2022 at 12:29 PM SHUBHAM SALUNKHE <
> [email protected]> wrote:
>
>> Hi All,
>>          I am trying to find memory leak using libmemunreachable library
>> in AOSP. i have getting following output on adb shell, but not able to find
>> line number of code where memory leak present or any backtrace logs in adb
>> logs. following commands are executed as mentioned in link
>> <https://android.googlesource.com/platform/system/memory/libmemunreachable/+/master/README.md#:~:text=libmemunreachable%20is%20a%20zero-overhead,differences%20to%20remove%20the%20overhead.>
>> .
>>
>> *Commands:-*
>> adb root
>> adb shell setprop libc.debug.malloc.program app_process
>> adb shell setprop wrap.[process] "\$\@"
>> adb shell setprop libc.debug.malloc.options backtrace=4
>> dumpsys -t 600 meminfo --unreachable [process].
>>
>> *adb shell output:-*
>>  Unreachable memory
>>   704 bytes in 5 unreachable allocations
>>   ABI: 'arm64'
>>
>>   288 bytes unreachable at 7862adf450
>>    first 20 bytes of contents:
>>    7862adf450: 88 13 e8 07 00 00 00 00 9e 9f 15 08 00 00 00 00
>> ................
>>    7862adf460: 2c bb 17 08 00 00 00 00 23 8a 89 08 00 00 00 00
>> ,.......#.......
>>
>>          No. of backtrace frames are 0 in debug logs.  is there any way
>> to enable backtrace in adb logs or to get line no. of source code from
>> above adb shell output.
>>
>> Thanks & Regards,
>> Shubham Salunkhe
>>
>> --
>> --
>> You received this message because you are subscribed to the "Android
>> Building" mailing list.
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Android Building" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/android-building/3f5dac22-6aad-4e6a-b840-8afc564fce28n%40googlegroups.com
>> <https://groups.google.com/d/msgid/android-building/3f5dac22-6aad-4e6a-b840-8afc564fce28n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAJgzZorr5L8C64xT%2B_QT77%2Bsz8Gjfysqu%2BucJg%2BbyP9eZ-wrWw%40mail.gmail.com.

Reply via email to