[Click] using click on mips (WRT54G)
Eddie Kohler
kohler at CS.UCLA.EDU
Tue Jan 25 12:33:00 EST 2005
Hi Tolja,
This actually *does not* look like an alignment fault! It looks like
the element that's generating the packets is including extra padding
bytes. That's definitely a mistake. Can you please send a full Click
script?
Eddie
On Jan 25, 2005, at 9:19 AM, Anatolij Zubow wrote:
> Hi Eddie,
>
> I solved this problem. It was indeed an alignment fault.
>
> Example:
>
> On Intel x86:
>
> Classifier(12/0806 20/0001,
> 12/0806 20/0002,
> 12/0800,
> -);
>
> On Mipsel like WRT54G:
>
> Classifier(16/0806 18/0001,
> 16/0806 18/0002,
> 16/0800,
> -);
>
> Greetings,
> Tolja
>
> Hi Anatolij,
>
> This is disappointing. Could you send the Click script you're using?
>
> Usually alignment problems manifest as "bus errors", not segmentation
> faults,
> but this may depend on the platform.
>
> Eddie
>
>
> Anatolij Zubow wrote:
>> Hi,
>>
>>
>>
>> We are currently working with (userlevel-) click on a mips platform
>> (WRT54G).
>>
>> Simple scripts like test-tun.click are working well. But when we use
> the
>>
>> Classifier click object, we get a segmentation fault. We also used the
>>
>> click-align tool with no success. Is this an alignment problem? What
>> could
>>
>> be a solution.
>>
>>
>>
>> BTW Is there an efficient way to debug click applications (without
> using
>> gdb)?
>>
>>
>>
>> Thanks,
>>
>> Anatolij
>>
>> _______________________________________________
>> 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
More information about the click
mailing list