Hi,
Are you writing driver on X86 or some other Architecture ? if it is X86
then use
*KEDR framework(http://kedr.berlios.de/ http://kedr.berlios.de/).*
*RegardsSanjeev Sharma*
On Mon, Mar 10, 2014 at 7:28 PM, valdis.kletni...@vt.edu wrote:
On Sun, 09 Mar 2014 22:14:24 -0700, m silverstri
2014-03-10 10:44 GMT+05:30 m silverstri michael.j.silvers...@gmail.com:
Hi,
I am developing a kernel driver. What should I test to make sure my
kernel driver is not leaking memory?
1. under normal operation (when applications open and close my driver
properly)
2. in error situation (when
Please use make menuconfig and press / then search for
DEBUG_KMEMLEAK_EARLY_LOG_SIZE and adjust value then save and exit.
You will find it under Kernel Hacking - Memory Debugging -| Kernel
memory leak detector
Symbol: DEBUG_KMEMLEAK_EARLY_LOG_SIZE
[=]
│ Type :
integer
│ Prompt: Maximum
On Sun, 09 Mar 2014 22:14:24 -0700, m silverstri said:
I am developing a kernel driver. What should I test to make sure my
kernel driver is not leaking memory?
1) The brute force method - just add lots of printk's that have
allocating 25-byte frobozz struct and freeing 25-byte frobozz struct
Hi,
I am developing a kernel driver. What should I test to make sure my
kernel driver is not leaking memory?
1. under normal operation (when applications open and close my driver properly)
2. in error situation (when application open my driver and then it
crashes without close my driver property)