Re: [boost] Re: Re: [ann] log viewer

From: John Torjo (john.lists_at_[hidden])
Date: 2004-04-28 12:21:12

Vladimir Prus wrote:

>John Torjo wrote:
>
>  
>
>>>I wonder if you've seen Chainsaw
>>>
>>>   http://logging.apache.org/log4j/docs/chainsaw.html
>>>
>>>and plan to compete with it or fix some weaknesses of it, or something
>>>else?
>>>
>>> 
>>>
>>>      
>>>
>>I wasn't aware of it. Anyway, I've downloaded and tested it.
>>(installing was quite hard, it took me a while)
>>    
>>
>
>Heh, I could not make it run yet ;-)
>
>  
>
it took a lot of guts and nerves ;)

>What I always wanted is some kind of 'debug dumps'. E.g. the program I work
>on now sometimes prints graphs into stdout in some textual representation.
>To view them, I need to copy paste from the log, and run two external
>programs. If would be nice of log viewer could quickly locate such 'dumps'
>and show them using customizable command sequence, or maybe C++ code.
>  
>
In case these debug dumps are logged into a file, and if I understood 
you correctly ;),
then it's possible to do so with the LogViewer I created.

I assume each such debug dump has a prefix (like, '[dbg]' or something) 
in order to differenciate it from something else.

Just drag-and-drop your log file into Easy LogView. Assuming the prefix 
is '[dbg]'.
Then, either locate one of such debug dump, and select the '[dbg]' word, 
right click and select "Existing Filter AND Containing Text..." or 
manually edit the filter, and add such a rule.
That's all! Then, you'll only see these debug dumps.

(of course, you can have as many filters as you wish, for your log file ;) )

>If we return to libraries side, it's highly desirable for logging library to
>support data dumps. The primary difference with logging is that for each
>dumped object, you need to presicely identify the name of object being
>logged.
>
>IOW, for two code lines:
>
>    log("lvk.flow") << "Entering some function";
>    dump("lvk.flow.paths.input") << graph;
>  
>
I'm not sure what you mean. What's wrong with:
log(whatever) << "lvk.flow.paths.input = " << graph;

>The first output can be formatted in any possible way, but the second should
>include "lvk.flow.paths.input" somewhere, so that it's possible to
>automatically extract it from the log.
>
>  
>
of course you can easily extract if from the log. Just use Easy LogViewer ;)

Best,
John

>- Volodya
>
>
>_______________________________________________
>Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>
>
>
>  
>