[Click] how to debug click?

[Michael Voorhaen]

I also suggest using valgrind (http://valgrind.org/). While it is a  
bit steep at first, you can use to check for mistakes in memory  
management (e.g. forgetting to free memory or reading out of bounds  
when parsing a packet) and profile a click script for Tasks that are  
taking up too much CPU. I regularly run it on all my C/C++ code to  
detect these kinds of problems in an early stage.

Groeten,
Michael

-------------------------
IBBT - PATS research group
Dept. of Mathematics and Computer Sciences
University of Antwerp
Campus Middelheim, G3.30
Middelheimlaan 1
B-2020 Antwerpen, Belgium
Phone: +32 (0)3 265.32.91
Fax: +32 (0)3 265.37.77
Web: www.pats.ua.ac.be/michael.voorhaen






On 01 Jul 2008, at 17:31, Beyers Cronje wrote:

> For userlevel Click you can use gdb. For information purposes I use
> click_chatter a lot to print statements to the screen. You can also  
> use the
> Print element in your configuration to "debug" packet flow.
>
> On Tue, Jul 1, 2008 at 4:21 PM, Yanfeng Zhang <threewells14 at gmail.com>
> wrote:
>
>> Hello,
>>
>> I am a beginner of click, and want to have an overall view of
>> click's structure, while I think debugging is a good way. Then, how  
>> to
>> debug
>> click? Should I use gdb or there is some other debugging tools?
>>
>> Thanks in advance!
>>
>> -Yanfeng
>> _______________________________________________
>> click mailing list
>> click at amsterdam.lcs.mit.edu
>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>>
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click