Hi.
For user space debugging: Valgrind would be the best tool (for checking memory leaks in user applications). For Kernel space debugging: Enabling Kmemleak for checking memory leaks in kernel space memory allocations. And of course we can go with gdb debugger also.
Thanks, Sudharshan S
Hi, Valgrind is the best option to find out memory corruption.
Along with Valgrind, you can use static analyzer like scan-build which will show the places where memory leaks or corruptions can happen.
Can someone please share the tool(s) except "cloc" for sloc.
Please let me know any open source c/c++ static code analysis tool, I need to use that tool for stataic analysis
There is a use case in which two machines are located in same network or different network but both are reachable to each other. Can remotely captured packets in one machine be seen in wireshark running in another machine on real time basis ?
Tool, which is having good performance, high Scalability and should revirew document as well
