[Security] Clarify that gdb is needed for elastic-endpoint memorydump

[natasha-moore-elastic]

Summary

Resolves #6119.

8.x docs updated in elastic/security-docs#7178

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: queued.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• reference/security/endpoint-command-reference.md

[github-actions]

✅ Vale Linting Results

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[github-actions]

Docs review summary

Focus areas

• Style and clarity: No issues. The note is concise and clearly states the Linux-specific requirement.
• Jargon: No issues. "GNU Debugger (GDB)" is appropriately expanded on first use.
• Frontmatter and applies_to: Not applicable to this change.
• Content type fit: Not applicable to this change.
• Parent issue satisfaction: Satisfied. The change directly addresses issue [Internal]: Elastic Endpoint memory dump add information about gdb #6119 by documenting that GDB must be installed on Linux to perform a memory dump.

Notes

• Vale linter found no issues with the modified lines.
• The note is appropriately placed immediately after the command description, making the prerequisite visible before users attempt the command.
• No inline comments needed; the change is ready to merge.

Generated by Docs review agent for issue #6623 · ● 577.8K · ◷