MemCapture
MemCapture contient 6 skills collectées depuis rdkcentral, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Analyze C++17 MemCapture code for memory safety issues including resource leaks, use-after-free, unclosed ifstream files, dangling iterators, and improper shared_ptr cycles. Use when reviewing metric code, file parsers, or report generation.
Verify MemCapture C++17 code is correct and portable across all supported RDK device platforms (AMLOGIC, AMLOGIC_950D4, REALTEK, REALTEK64, BROADCOM, MEDIATEK). Use when reviewing platform-specific metric code, adding a new platform target, or auditing sysfs/proc path assumptions.
Run comprehensive quality checks (static analysis, memory safety, thread safety, build verification) on the MemCapture codebase. Use when validating code changes or debugging before committing.
Analyze MemCapture C++17 code for thread safety issues including race conditions on shared metrics maps, deadlocks in metric shutdown, improper std::atomic usage for mQuit flags, and collection thread lifecycle problems. Use when reviewing concurrent metric code or debugging threading issues.
Triage MemCapture behavioural issues by correlating the HTML/JSON report output and stderr logs with the MemCapture source tree. Covers metric collection failures, missing data in reports, platform-specific sysfs/proc read errors, process grouping problems, and report generation issues. The user states the issue; this skill guides systematic root-cause analysis.