This comprehensive training for software technical support engineers, system administrators, DevOps, software developers and testers, site reliability and performance engineers teaches the analysis of all memory spaces for patterns of abnormal software behavior in process, kernel, and complete (physical) memory dumps and features:

Anolog.io is our latest cloud project for anomaly detection in software traces and logs. It consists of 4 main elements:

35 years ago:

"Considerable time, resources and money now lost on unorganized, trial-and-error approaches to storage dump debugging ..."

Daniel H. Rindfleisch, Author of "Debugging System 360/370 Programs Using OS And VS Storage Dumps"

Since then, software became much more complex and widespread. Unfortunately, today we can still quote the same phrase:

Huge amount of "time, resources and money now lost on unorganized, trial-and-error approaches to [memory] dump debugging".

Learn how to analyze application crashes and freezes, navigate through process memory dump space and diagnose corruption, memory leaks, CPU spikes, blocked threads, deadlocks, wait chains, and much more. We use a unique and innovative pattern-oriented analysis approach to speed up the learning curve. The training pack consists of practical step-by-step exercises using GDB and LLDB debuggers highlighting dozens of memory analysis patterns diagnosed in 64-bit process memory dumps from Mac OS X and Linux platforms.

This comprehensive training is for security researchers, malware and digital forensic analysts who have never used WinDbg debugger from Microsoft Debugging Tools for Windows for the analysis of computer memory. The course is also useful for technical support and escalation engineers who analyse memory dumps from complex software environments and need to delve deeper into abnormal software structure and behavior. The training pack features:

Adding AI. Analysis Improvement.

Problem: You are not satisfied with a crash analysis report.

Problem: You are a novice and need expert pattern-oriented analysis of your crash and hang memory dump files or debugger logs.

Problem: Your critical issue is escalated to the VP level. Engineers analyze memory dumps and software traces. No definite conclusion so far. You want to be sure that nothing has been omitted from the analysis.