Memory Analyzer

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
Kortath
Member
Member
Posts: 57
Joined: Sat Sep 07, 2013 11:23 am

Memory Analyzer

Post by Kortath »

What would you all recommend as a good Memory Analyzer to check your OS kernel file ? I have seen many out there, but I really hadn't seen one that stands out above the rest. I am wanting to verify leaks in the kernel file. I am wanting to make sure its solid.
User avatar
dozniak
Member
Member
Posts: 723
Joined: Thu Jul 12, 2012 7:29 am
Location: Tallinn, Estonia

Re: Memory Analyzer

Post by dozniak »

Since this is a kernel land, you'll have to make your own logging memory allocator(s).
Learn to read.
Kortath
Member
Member
Posts: 57
Joined: Sat Sep 07, 2013 11:23 am

Re: Memory Analyzer

Post by Kortath »

dozniak wrote:Since this is a kernel land, you'll have to make your own logging memory allocator(s).

Yea I was afraid of that. I was looking for the "quick fix". I should know better then that. Thanks for the reply.
User avatar
dozniak
Member
Member
Posts: 723
Joined: Thu Jul 12, 2012 7:29 am
Location: Tallinn, Estonia

Re: Memory Analyzer

Post by dozniak »

Kortath wrote:Yea I was afraid of that. I was looking for the "quick fix". I should know better then that. Thanks for the reply.
If you want to do a little bit of ahead-of-time analysis, then look into "static code analyzer" like clang static-analyzer, PVS-Studio or Coverity. They are able to spot most logic errors in memory management before you even run your code.

It isn't a panacea, but very useful debugging tool anyway.
Learn to read.
Kortath
Member
Member
Posts: 57
Joined: Sat Sep 07, 2013 11:23 am

Re: Memory Analyzer

Post by Kortath »

dozniak wrote:
Kortath wrote:Yea I was afraid of that. I was looking for the "quick fix". I should know better then that. Thanks for the reply.
If you want to do a little bit of ahead-of-time analysis, then look into "static code analyzer" like clang static-analyzer, PVS-Studio or Coverity. They are able to spot most logic errors in memory management before you even run your code.

It isn't a panacea, but very useful debugging tool anyway.

Haha, goddess of healing. I love it.

Yea I have heard of coverity, never tried it. Static Code Analyzer. That sounds more like what I am after. Cool beans !!
Post Reply