extrospect-beam | live extrospection of the Erlang BEAM VM — WARNING

In general, the --pstack mode for erlang-sample is useful for troubleshooting, since it prints full stack traces at a time and one can easily see many common problems (such as all traces being a single entry deep, or no Erlang functions ever appearing). If the problem is just that the register information is more complex than a single location (you can check with dwarfdump, readelf or similar), it's mostly a matter of making erlang-sample smarter. If the location isn't there at all, though, (i.e. gdb gives the dreaded (optimized out) message when you do info address c_p when stopped in process_main) you can find this and other important registers by looking at the disassembly of process_main.