[Click] Seg fault in IPFilter

[Michael Voorhaen]

I use either gdb or ddd (graphical frontend for gdb) as a debugging 
tool, which has helped me a lot. Next to that valgrind can also be 
useful to trace memory leaks. Regards,
Michael


Quoting Beyers Cronje <bcronje at gmail.com>:

> Now for a back to basics question from myself, what tools/techniques do you
> guys use to debug click ? The question stems from the fact that I really
> have very little experience on programming in the linux/*nix environment and
> the only time I ever spend on linux is when I'm working on Click. So you can
> say I've been spoiled with integrated debuggers on Visual Studio and
> Builder, Windbg etc.
>
> Up to now I've only used click_chatter() for debugging in Click, and due to
> the excellent modular framework of Click this has worked out quite nicely
> for me. But I'm wondering if there are better ways to go about it? Sometimes
> I miss not being able to use breakpoints and stepping through the code.
>
> Cheers
>
> Beyers
>
> On 4/5/06, Alastair McKinley <amckinley03 at qub.ac.uk> wrote:
>>
>> Beyers Cronje wrote:
>>
>> > Hi Alastair,
>> >
>> > To use IPFilter input packets must have their IP header annotation
>> > set, so use CheckIPHeader or MarkIPHeader before input to IPFilter.
>> >
>> > Cheers
>> >
>> > Beyers
>> >
>> Thanks Beyers,
>>
>> I should have thought back to basics before I thought that something
>> more sinister was going on.
>>
>> Unfortunately I still have a problem with my elements, but at least I
>> can (try to) debug them at userlevel.
>>
>> Thanks a lot!
>>
>> Alastair
>>
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.