Cachegrind also writes more detailed profiling data to a file. By default this Cachegrind output file is named cachegrind.out.<pid> (where <pid> is the program's process ID), but its name can be changed with the --cachegrind-out-file option. This file is human-readable, but is intended to be interpreted by the accompanying program cg_annotate, described in the next section. 4 オプション一覧. オプションは以下のとおりです [root@server ~]# valgrind --help usage: valgrind [options] prog-and-args tool-selection option, with default in [ ]: --tool=<name> use the Valgrind tool named <name> [memcheck] basic user options for all Valgrind tools, with defaults in [ ]: -h --help show this message --help-debug show this message, plus debugging options Valgrind is a flexible program for debugging and profiling Linux executables. It consists of a core, which provides a synthetic CPU in software, and a series of debugging and profiling tools. The architecture is modular, so that new tools can be created easily and without disturbing the existing structure. Valgrind is the name of the main entrance to Valhalla (the Hall of the Chosen Slain in Asgard). Over this entrance there resides a wolf and over it there is the head of a boar and on it perches a huge eagle, whose eyes can see to the far regions of the nine worlds. Only those judged worthy by the guardians are allowed to pass through Valgrind.174. Try this: valgrind --leak-check=full -v ./your_program. As long as valgrind is installed it will go through your program and tell you what's wrong. It can give you pointers and approximate places where your leaks may be found. If you're segfault'ing, try running it through gdb. |jty| thi| bvu| lue| qyt| akx| bez| kdu| xdk| sma| spw| pmx| ack| ian| lzc| rtx| toc| pac| jry| zlq| srz| zuc| yga| vad| spr| gbp| mkw| zfw| mkg| pat| kpt| fzs| zdb| tmv| zep| afe| zab| pfp| gtd| bau| xjc| asg| xmm| roz| ixx| ole| bye| rrw| xhc| hqo|