debug-guide.md added memory statistics command

[rob-deutsch]

This would've been valuable to me while investigating #5530.

I discovered that more debug commands are also available, but I don't know enough about them to add them myself (e.g. debug/pprof-mutex, debug/metrics/prometheus).

[schomatis]

Thanks @rob-deutsch! Could you add a link to the memstats object you're referring to, and also if possible, what interesting information a user might find in it? (e.g., how did it help your particular debug scenario)

[rob-deutsch]

Thanks @schomatis, resubmitted with suggested additions.

[schomatis]

Great!

[schomatis]

nit: could you also add an entry in the "Table of Contents" above pointing here?

[rob-deutsch]

Drat, my bad, will do

[rob-deutsch]

... I also noticed (and fixed) the inconsistent spelling of analyse/analyze, just to make it a tad neater.

[schomatis]

... I also noticed (and fixed) the inconsistent spelling of analyse/analyze, just to make it a tad neater.

I think they are both right but "analyze" is the accepted American spelling.

[rob-deutsch]

In the case of ambiguity I tend to prefer British English, but some after some Googling I learned that US English is generally accepted for this kind of purpose.

Resubmitted with US English and a small frown of disapproval 😉

[schomatis]

Thanks for fixing the "stack dump" entry also! Beyond the call of duty 🎖️

[Kubuxu]

There is also a much simpler option for non-linux folks to download most of the info: going to localhost:5001/debug/pprof/ and doing Save as on the links.

Not blocking this PR in any regard, just mentioning it as I discovered it recently.

---

EDIT: localhost:5001/debug/ -> localhost:5001/debug/pprof/

[rob-deutsch]

I'm getting a 404 error on localhost:5001/debug/. That sounds like a handy feature though, can we integrate that to master?

[Kubuxu]

Sorry: localhost:5001/debug/pprof/.

Unfortunately no vars there.