Re: [leaf-devel] images and valgrind

2014-12-30 Thread kp kirchdoerfer
Am Montag, 29. Dezember 2014, 21:15:47 schrieb Andrew: > Hi. > Yes, valgrind is mostly useful for developers (I ported it due to bird > crashes diagnostics). > But oprofile with kernel debuginfo is widely used, for ex., for > high-load routers tuning. Ok, I changed buildscripts to remove valgrind.

Re: [leaf-devel] images and valgrind

2014-12-29 Thread Erich Titl
Hi KP Am 29.12.2014 um 19:09 schrieb kp kirchdoerfer: > Hi all; > > as you mave seen; I've released beta1 for Bering-uClibc 5.1.3 today. > > With the addition of valgrind.lrp the images are about 110MB, where > valgrind.lrp with 13MB is more then 10% of the image size. > As valgrind is only use

Re: [leaf-devel] images and valgrind

2014-12-29 Thread Andrew
Hi. Yes, valgrind is mostly useful for developers (I ported it due to bird crashes diagnostics). But oprofile with kernel debuginfo is widely used, for ex., for high-load routers tuning. 29.12.2014 20:09, kp kirchdoerfer пишет: > Hi all; > > as you mave seen; I've released beta1 for Bering-uClib

[leaf-devel] images and valgrind

2014-12-29 Thread kp kirchdoerfer
Hi all; as you mave seen; I've released beta1 for Bering-uClibc 5.1.3 today. With the addition of valgrind.lrp the images are about 110MB, where valgrind.lrp with 13MB is more then 10% of the image size. As valgrind is only useful for developers, I thought about restrictions for images, where d