This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
RE: How can I trace when the allocated memory is free after kmalloc ?
Hi,
I tested probe vm.kfree on Android + kernel 3.0 with systemtap v1.5 and it works fine (prints pointer correctly and tapset "name" variable correctly). With kernels 2.6.35 and 2.6.38, I used to have globally more instabilities so that would require debugging, as mentioned by Mark.
Regards
Fred
Frederic Turgis
OMAP Platform Business Unit - OMAP System Engineering - Platform Enablement
>
Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920
-----Original Message-----
>From: Josh Stone [mailto:jistone@redhat.com]
>Sent: Tuesday, September 20, 2011 6:01 PM
>To: ììíB
>Cc: Mark Wielaard; Turgis, Frederic; systemtap@sourceware.org
>Subject: Re: How can I trace when the allocated memory is free
>after kmalloc ?
>
>On 09/20/2011 02:12 AM, Mark Wielaard wrote:
>> On Tue, 2011-09-20 at 09:38 +0900, ììíB wrote:
>>> But vm.kfree is not working. ( make target phone reset ) (
>>> vm.kmalloc is ok .)
>>>
>>> Below is my test code .
>>>
>>> -------------------------------------
>>> probe vm.kfree { println(vm.kfree \n")}
>>> -------------------------------------
>>>
>>> please recommand what I should try .
>>
>> Try getting a serial console to to read out the kernel messages.
>> I don't know how that works on your android based system,
>but here are
>> some generic linux kernel setups:
>> http://sourceware.org/systemtap/wiki/DeveloperSetupTips
>
>In Android, there's usually a /proc/last_kmsg with the kernel
>buffer from before the reboot.
>