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

Jayson Vantuyl kagato@REDACTED
Thu Jan 14 05:05:39 CET 2010

Selective debugging is one of Erlang's high points.

If the bug often bites the a particular user, seqtoken allows  
debugging to follow a single request. Use that infrastructure to debug  
just that user.

Otherwise, you can also attach a matchspec to debug patterns, so you  
may be able to carefully craft a match to catch the broken behavior at  
some point in the system.

Sent from my iPhone

On Jan 13, 2010, at 7:09 PM, Kaiduan Xie <kaiduanx@REDACTED> wrote:

> 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.
> You can not turn on the debug log that will bring the system down, and
> Erlang trace will not help since the problem is non-reproducible or
> hard to reproduce.
> How to resolve this kind problem? Can you shed light on this?
> Thanks,
> kaiduan
> ________________________________________________________________
> erlang-questions mailing list. See http://www.erlang.org/faq.html
> erlang-questions (at) erlang.org

More information about the erlang-questions mailing list