![]() How Ptrcheck Works: Stack and Global Checks 11.5. Ptrcheck: an experimental heap, stack and global array overrun detector 11.1. Interpreting "Aggregated access counts by offset" data 10.3. Interpreting the acc-ratios fields 10.2.3. Interpreting the max-live, tot-alloc and deaths fields 10.2.2. Using the POSIX Threads API Effectively 8.3.1. Hints and Tips for Effective Use of DRD 8.3. Detected Errors: Misuse of the POSIX threads API 8.2.5. Multithreaded Programming Problems 8.1.4. Multithreaded Programming Paradigms 8.1.2. Hints and Tips for Effective Use of Helgrind 7.6. Helgrind's Race Detection Algorithm 7.4.3. Detected errors: Inconsistent Lock Orderings 7.4. Detected errors: Misuses of the POSIX pthreads API 7.3. callgrind_control Command-line Options 7. callgrind_annotate Command-line Options 6.6. Limiting the range of collected events 6.2.3. Multiple profiling dumps from one program run 6.2.2. Callgrind: a call-graph generating cache and branch prediction profiler 6.1. The Global and Function-level Counts 5.2.6. Using Cachegrind, cg_annotate and cg_merge 5.2.1. Cachegrind: a cache and branch-prediction profiler 5.1. What to expect when using the wrappers 5. Building and installing the wrappers 4.8.2. Debugging MPI Parallel Programs with Valgrind 4.8.1. Memory Pools: describing and working with custom allocators 4.8. ![]() Details of Memcheck's checking machinery 4.5.1. ![]() Overlapping source and destination blocks 4.2.7. When a heap block is freed with an inappropriate deallocationįunction 4.2.6. ![]() Use of uninitialised or unaddressable values in systemĬalls 4.2.4. Illegal read / Illegal write errors 4.2.2. Explanation of error messages from Memcheck 4.2.1. Limitations - original function signatures 3.2.7. Using and understanding the Valgrind core: Advanced Topics 3.1. What Valgrind does with your program 2.2. Using and understanding the Valgrind core 2.1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |