Lines Matching full:program
125 <para>When the program exits, Valgrind runs the procedure
138 program runs.</para>
144 <para>My (buggy) program dies like this:</para>
153 invalid writes or invalid frees in your program, the above may
154 happen. Reason is that your program may trash Valgrind's low-level
156 something similar. The cure is to fix your program so that it
164 <para>My program dies, printing a message like this along the
169 <para>One possibility is that your program has a bug and erroneously
187 <para>I tried running a Java program (or another program that uses a
209 <para>Apart from this, in theory Valgrind can run any Java program
230 <para>My program uses the C++ STL and string classes. Valgrind
232 the exit of the program, but there should be none.</para>
240 freed at the exit of the program cause Valgrind to report this
246 Beware! Doing so will probably slow down your program, sometimes
257 running your program.</para>
297 object is unloaded before the program terminates, Valgrind will
383 <para>My program crashes normally, but doesn't under Valgrind, or vice
387 <para>When a program runs under Valgrind, its environment is slightly
392 particularly if your program is buggy. For example, if your program
395 Valgrind. Alternatively, if your program has data races, these may not
400 native execution environment. In the case where your program crashes
410 <para> Memcheck doesn't report any errors and I know my program has
417 program spawns children, they won't be traced by Valgrind
418 by default. Also, if your program is started by a shell script,
430 program to listen on that port:</para>
438 <para>Second, if your program is statically linked, most Valgrind
445 when you know your program calls <function>malloc</function>. The
446 workaround is to avoid statically linking your program.</para>
454 program?</para>
518 <para>"definitely lost" means your program is leaking memory --
522 <para>"indirectly lost" means your program is leaking memory in
530 <para>"possibly lost" means your program is leaking
538 <para>"still reachable" means your program is probably ok -- it
573 cause. This requires editing, compiling and re-running your program
589 <para>Is it possible to attach Valgrind to a program that is already
599 program without any instrumentation (which involves a slow-down of about
604 <computeroutput>callgrind_control</computeroutput> program for details.
