servers with huge state terms

[Luke Gorrie]

Ahoy,

I have a server process (gen_fsm) whose state is a very large
term. This is a problem because when I get a crash report it's really
long and hard to read - I've done things like ask xterm to have a
thousand-line scrollback as a workaround.

I'm tempted to move the larger parts of the state into an ets table
(which would be pretty suitable, but I prefer the tuple) so that the
server's state is more stringifyable - but does anyone know another
approach for this sort of thing?

Cheers,
Luke