debugging-tools

To find memory leaks using the Node.js inspector, take and compare heap snapshots to isolate retaining objects. This workflow pinpoints the failing component by revealing what prevents garbage collection during the reproduction step.

Debug slow React pages using Chrome DevTools by recording performance and interpreting Flame Charts and Long Tasks. This isolates slow code paths by visualizing execution timing during reliable issue reproduction.

Trace failing syscalls and file operations using strace to monitor low-level OS interactions. This identifies missing configurations, failing system calls, and unexpected runtime behavior without modifying the application source code.

You can use lldb or gdb to analyze core dumps from native binary crashes. This crash analysis workflow inspects memory state and call stacks at the moment of failure to isolate the failing native component.

Troubleshoot network handshake and request timing problems using curl and packet capture tools. This isolates network-layer failures by verifying request headers, response codes, and handshake protocols during issue reproduction.

Isolate application bugs by reliably reproducing the issue and applying binary search to bisect the search space. This disciplined workflow uses tool-specific steps like conditional breakpoints and logpoints to confirm hypotheses.