[erlang-questions] Non-reproducible bug on a live erlang system

Attila Rajmund Nohl attila.r.nohl@REDACTED
Thu Jan 14 16:35:31 CET 2010

2010/1/14, Kaiduan Xie <kaiduanx@REDACTED>:
> Hi, all,
> Consider the following case, you have a live/busy Erlang system in
> production which handles thousands of transactions per second and
> millions of users, and customer reported a non-reproducible bug. The
> problem is non-reproducible, or intermittent, or very hard to
> reproduce in live system and in lab.

Does this bug involve a crash report with a stack trace? You can
always add some assert-like statements (i.e. if you know that a
variable must not bound to the 'undefined' atom at a certain point in
the code, you can add something like 'Variable /= undefined') where
you think something is wrong.

More information about the erlang-questions mailing list