Still if its possible with the help of valgrind to find the leak and patch it, that would mean more stability so its better to help out and find the problem instead of just pointing out how long it would take to fill up the mem
valgrind crashes when trying to debug watchdog. A web search shows other people having the exact same crash when trying to debug an ARM binary linked with uclibc, and nobody seemed to care enough to investigate. So that's a no-go.
valgrind crashes when trying to debug watchdog. A web search shows other people having the exact same crash when trying to debug an ARM binary linked with uclibc, and nobody seemed to care enough to investigate. So that's a no-go.
Erm - that's a hint...
maybe uclibc is the problem?
It's crashing right at start time, so this is unrelated to the leak in any way, and is a commonly mentioned issue based on a quick Google search.
exactly - see why the arm is crashing...
That's the valgrind's author problem to investigate, not mine.
Asus ARM routers. 380 series FW. Memory leak in /sbin/watchdog process.
I havnt got the dpi engine in my build
admin@Aurora:/tmp/home/root# cat /proc/$(pidof watchdog)/status|grep VmRSS
VmRSS: 1272 kB
5 mins later
admin@Aurora:/tmp/home/root# cat /proc/$(pidof watchdog)/status|grep VmRSS
VmRSS: 1276 kB
We use essential cookies to make this site work, and optional cookies to enhance your experience.