[erlang-questions] Tracing frameworks

Lennart Öhman Lennart.Ohman@REDACTED
Fri Apr 13 10:54:26 CEST 2007

I believe dbg will always be there for the expert programmer
knowing his/her trace commands.
Inviso replaces trace tool builder in combination with dbg and
is far (too) more advanced.
It is still however in version 0 release. I am working on it
as "we speak". The equivalent to trace tool builder is comming
soon as an add on on-top of inviso, making it possible to
build an inviso adaptation for your system.
I do also actually have an inofficial not yet ready GS based
gui interface to inviso, meant to be a desktop tool for the
programmer not on speaking terms with dbg. It is to be seen
when that tool is released however.
Best Regards
(And then not to mention all new interesting problems comming
when running SMP... :-)
Lennart Ohman                   phone   : +46-8-587 623 27
Sjöland & Thyselius Telecom AB  cellular: +46-70-552 6735
Hälsingegatan 43, 10 tr         fax     : +46-8-667 8230
SE-113 31 STOCKHOLM, SWEDEN     email   : lennart.ohman@REDACTED


Från: erlang-questions-bounces@REDACTED genom Vlad Dumitrescu
Skickat: fr 2007-04-13 10:05
Till: erlang-questions
Ämne: [erlang-questions] Tracing frameworks


I was looking at the available tracing tools and I am a little
confused. I hope someone can shed some light on these questions.

The "classic" way involves using dbg, a newer way is with observer/ttb
and even newer is inviso. One has to chose between those, because they
all use the built-in tracing mechanism. Are there any guidelines as to
what use cases are most interesting for each tool?

Regarding ttb, why is only a file trace port supported? For a
distributed setting, I guess it is much easier to be able to sort

Is it just me, or would a tool that is easier to use be something to wish for?

best regards,
erlang-questions mailing list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20070413/62e846f5/attachment.htm>

More information about the erlang-questions mailing list