redpanda
redpanda copied to clipboard
automatic stack trace decoding
We need to be able to have meaningful stack traces on crash without copying and pasting raw traces into a decoding utility.
should be under rpk debug stracktrace
Perhaps ideally we can just send a debug bundle with a nicely formatted trace when this happens (including an abort, e.g. OOM)
cc @rkruze
In order to get nice traces remotely we'd need to ship all the debug symbols which is probably a non-starter. Once devprod starts hosting the decoding webapp the overhead of copy/paste is tiny. It even has an API so that could be integrated into rpk some how.
We could probably close this ticket.
Since we now abort on bad allocs, could we on the abort send a message back saying where this happened? It might give us some insights into the scenarios in which we run into bad allocs.