This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Re : Re: How can I trace when the allocated memory is free after kmalloc ?
Hi,
On Sun, Sep 18, 2011 at 10:08:32PM +0900, ììí wrote:
> <html>
> <head>
> <meta http-equiv="content-type" content="text/html; charset=UTF-8">
> <title>new doc</title>
> <style>
> [...]
Please don't send HTML emails, they are really hard to read.
> <p>Speaking in detail, I have tried only one proble "probe vm.kmalloc"
> , and it is ok.</p>
> <p>and I have tried the "proble vm.kfree" , and it make my android
> phone reset.</p>
> <p>Here is the test code.</p>
> <p> </p>
> <p>probe vm.kmalloc { println("vm.kmalloc")}</p>
> <p>probe vm.kfreee { priinln("vm.kfree")}</p>
> <p> </p>
> <p>So, could you recommend some way to resolve the problem?</p>
> <p>( probe kerne.function("kfree") also make my phone reset
> . )</p>
> <p> </p>
> <p>Below is the my environment .</p>
> <p>- target : android phone : kernel ver : 2.6.35.11</p>
> <p>- host : ubuntu 11.04 , 64 bit</p>
> <p>- arch=arm</p>
That must be something ubuntu or arm specific.
The same works fine on my x86_64 fedora 2.6.35 kernel based system.
Cheers,
Mark