Learn to say popular low-level debugging and performance profiling tool names correctly.
0 / 5 completed
1 / 5
How is GDB (GNU Project Debugger, the standard command-line debugger for C and C++) correctly pronounced?
GDB is pronounced 'JEE-DEE-BEE' — every letter spoken individually, G-D-B. In a technical interview: "GDB let me set a breakpoint on that function and inspect every local variable the moment it crashed."
2 / 5
How is LLDB (modern debugger built on the LLVM project, the default debugger on macOS) correctly pronounced?
LLDB is pronounced 'EL-EL-DEE-BEE' — every letter spoken individually, L-L-D-B. In a technical interview: "LLDB stepped through the Swift code and printed the exact line where the optional force-unwrap failed."
3 / 5
How is Valgrind (instrumentation framework for detecting memory errors and profiling programs) correctly pronounced?
Valgrind is pronounced 'VAL-grynd' — stress on VAL, rhymes loosely with 'find'. In a technical interview: "Valgrind flagged the exact malloc call that never got freed, hidden three function calls deep."
4 / 5
How is strace (Linux diagnostic tool that traces system calls made by a running process) correctly pronounced?
strace is pronounced 'ES-trays' — 'S' spoken as the letter plus 'trace'. In a technical interview: "strace showed me the process was blocked on a file open call to a path that didn't even exist."
5 / 5
How is perf (Linux profiling tool used for performance analysis and CPU counter sampling) correctly pronounced?
perf is pronounced 'PURF' — one syllable, short for 'performance'. In a technical interview: "perf sampled the CPU stack a thousand times a second and showed exactly which function was burning the cycles."