![]() ![]() Valgrind gdbserver thread information 3.2.8. Examining and modifying Valgrind shadow registers 3.2.9. Limitations of the Valgrind gdbserver 3.2.10. ![]() ![]() Limitations - original function signatures 3.3.7. Explanation of error messages from Memcheck 4.2.1. Illegal read / Illegal write errors 4.2.2. Use of uninitialised or unaddressable values in systemĬalls 4.2.4. When a heap block is freed with an inappropriate deallocationįunction 4.2.6. Overlapping source and destination blocks 4.2.7. Details of Memcheck's checking machinery 4.5.1. Memory Pools: describing and working with custom allocators 4.9. Debugging MPI Parallel Programs with Valgrind 4.9.1. Building and installing the wrappers 4.9.2. What to expect when using the wrappers 5. Cachegrind: a high-precision tracing profiler 5.1. ![]() Global, File, and Function-level Counts 5.2.6. Differencing Cachegrind output files 5.2.11. Callgrind: a call-graph generating cache and branch prediction profiler 6.1. Multiple profiling dumps from one program run 6.2.2. Limiting the range of collected events 6.2.3. callgrind_control Command-line Options 7.Ĭallgrind_annotate Command-line Options 6.7. Detected errors: Misuses of the POSIX pthreads API 7.3. Detected errors: Inconsistent Lock Orderings 7.4. Helgrind's Race Detection Algorithm 7.4.3. Hints and Tips for Effective Use of Helgrind 7.6. Multithreaded Programming Paradigms 8.1.2. Multithreaded Programming Problems 8.1.4. Detected Errors: Misuse of the POSIX threads API 8.2.5. Hints and Tips for Effective Use of DRD 8.3. Using the POSIX Threads API Effectively 8.3.1. Nulgrind: the minimal Valgrind tool 12.1. BBV: an experimental basic block vector generation tool 13.1. Using Basic Block Vectors to create SimPoints 13.3. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |