On Fri, Mar 6, 2009 at 6:05 AM, Anlin Zhang <[email protected]> wrote: > Hi, > > We run valgrind in back ground like this: > > nohup valgrind --log-file=/opt/log/MyApp.val.log --error-limit=no -v > /opt/bin/MyApp & > > The MyApp is a server handling client requests through TCP. But it sometimes > crash (randomly) so we want to use valgrind to debug. > > But after some time the log file size stops increasing. MyApp is still > running as it is still responding to the client programs' request. We > haven't re-produced the crash with valgrind so far. > > I'm wondering if it's normal or something wrong with our setup.
It's hard to know what could be wrong with this limited information. But if MyApp is still running then Valgrind must also still be running. And you're using --error-limit=no. It could just be that Valgrind isn't finding anything more worth complaining about. It might be worth addressing any Valgrind complaints that are present in the log file. Nick ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
