The problem with valgrind is the same as the general problem with gdb; init needs to be pid 1, and these processes then can't trace it/emulate it.
Scott On Wed, Jun 8, 2011 at 12:19 PM, Evan Huus <[email protected]> wrote: > After the discussion recently around running static code analysis on > upstart, my mind automatically went to the other analysis tool I use > the most: valgrind. > > A quick google reveals [1], which suggests it doesn't work > out-of-the-box, but I'm not familiar enough with valgrind's internals > to know how fatal or fixable that problem actually is. > > If anyone else has tried this I'd love to know. If not then I might > see if I can find the time to take a look. > > Cheers, > Evan > > [1] > http://stackoverflow.com/questions/3887723/upstart-init-is-leaking-memory-how-do-you-debug-it > > -- > upstart-devel mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/upstart-devel >
-- upstart-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
