Re: kill the process cause system crash
Philippe Waroquiers <[email protected]>
| Newsgroups | gmane.comp.debugging.valgrind |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 2019-12-19 at 17:32 +0000, Rachel Chen (rychen) wrote: > Hi Philippe, > > Thanks for your help! > > I am running this on a linux switch. What CPU ? What version of linux ? > The Valgrind I am using is 2.15. 2.15 is not a known valgrind version. The valgrind version can be retrieved doing: valgrind --version Recent valgrind will give a more extended version doing: valgrind --version -v > There is no error message/output when the crash happens. It was not clear to me that the whole system (kernel) crashed, I thought you were speaking about your "application system" crashing. valgrind is supposed to be a 'normal' user level process, so if ever valgrind crashes the kernel, then that is a kernel bug :). Note that valgrind takes a lot of resources (memory/cpu), that might put some stress on the system. > But I noticed after the system bootup again, the valgrind log file seems do have some info there... > > I will check the link below to see if I can trigger memory leak search without killing the process. Ok. Note that the given links document the last released version of valgrind. Philippe > > Thanks, > Rachel > > > On 12/18/19, 10:42 PM, "Philippe Waroquiers" <[email protected]> wrote: > > On Thu, 2019-12-19 at 00:19 +0000, Rachel Chen (rychen) via Valgrind-users wrote: > > Hello, > > > > I am using Valgrind to debug a memory leak. Somehow when I try to kill the process to get the log file with memory leak, it crash the system. I am using the following command to get the pid and kill the pid: > > > > Ps -ef | grep valgrind. è to get the pid > > Kill <pid> > > > > Any idea what might be wrong here? Thanks for the help in advance! > > > > Thanks, > > Rachel > > Some more information is needed : > * which platform ? > * which version of valgrind ? > * what is the error message/output when the crash happens ? > > Note that you can trigger memory leak search from the shell (or from gdb) > by using vgdb, without killing your process. > > See the below links for more information. > > http://www.valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.valgrind-monitor-commands > > http://www.valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver-commandhandling > > http://www.valgrind.org/docs/manual/mc-manual.html#mc-manual.monitor-commands > > Philippe > > > > _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users