[Click] Problem while running OLSR on Click
Eddie Kohler
kohler at cs.ucla.edu
Mon Jan 17 20:00:24 EST 2011
Abhishek,
I do believe that checkins since v1.8.0 may have fixed this problem, so
if you could update to current git and check, that would be great.
Eddie
On 1/17/11 4:46 PM, Abhishek Chanda wrote:
> Hi,
>
> The problem was that the interface eth0 was down while eth1 was working.
> It is working fine if I change the interface name.
> I am using Click 1.8.0, the OS is Ubuntu 10.0 and the ./configure
> invocation is
> ./configure --enable-olsr --enable-local
>
> Thanks
>
> On Sun, Jan 16, 2011 at 9:09 PM, Eddie Kohler <kohler at cs.ucla.edu
> <mailto:kohler at cs.ucla.edu>> wrote:
>
> Abhishek,
>
> Which version of Click are you using? And on which operating
> system, and with which ./configure invocation? I feel like this
> might be an old bug.
>
> Eddie
>
>
>
> On 1/14/11 5:31 PM, Abhishek Chanda wrote:
>
> Hi,
>
> Thanks for the replies.
> Here is the stacktrace:
>
> (gdb) run test.click
> Starting program: /usr/local/bin/click test.click
> [Thread debugging using libthread_db enabled]
> click: ../include/click/vector.hh:184: void*&
> Vector<void*>::operator[](int): Assertion `i>=0&& i<_n' failed.
>
> Program received signal SIGABRT, Aborted.
> 0xffffe410 in __kernel_vsyscall ()
> (gdb) backtrace
> #0 0xffffe410 in __kernel_vsyscall ()
> #1 0xb7d3cef5 in raise () from /lib/i686/cmov/libc.so.6
> #2 0xb7d3e871 in abort () from /lib/i686/cmov/libc.so.6
> #3 0xb7d360ee in __assert_fail () from /lib/i686/cmov/libc.so.6
> #4 0x081eb510 in Vector<void*>::operator[] (this=0x8280b88,
> more_tasks=false) at ../include/click/vector.hh:184
> #5 Vector<void*>::at (this=0x8280b88, more_tasks=false) at
> ../include/click/vector.hh:186
> #6 Vector<Element*>::operator[] (this=0x8280b88,
> more_tasks=false) at
> ../include/click/vector.hh:299
> #7 Master::run_selects_poll (this=0x8280b88, more_tasks=false) at
> ../lib/master.cc:851
> #8 0x081ded53 in RouterThread::run_os (this=0x8280cd8) at
> ../lib/routerthread.cc:420
> #9 RouterThread::driver (this=0x8280cd8) at
> ../lib/routerthread.cc:510
> #10 0x081bb8ea in main (argc=Cannot access memory at address 0x3e34
> ) at click.cc:568
>
> The file test.click has
> FromDevice(eth0) -> Discard;
> I will try to see if I can provide more information on this.
>
> Thanks
>
> On Fri, Jan 14, 2011 at 11:28 AM, Viet Do Thi
> Minh<viet at q2s.ntnu.no <mailto:viet at q2s.ntnu.no>> wrote:
>
> Hi,
>
> I think that is not a bug in OLSR code. Actually, I run OLSR
> with
> nsclick and I got that error when I wrote a new element. The
> error was
> fixed when I corrected the code of the new element.
>
> Cheers,
> Viet
>
>
> On 1/14/2011 11:40 AM, Bart Braem wrote:
>
> Hi,
>
> If that's the bug in our OLSR code, would you mind
> sending a patch? It
>
> would help other future users.
>
>
> thanks,
> Bart
>
> On 14 Jan 2011, at 10:23, Viet, Do Thi Minh wrote:
>
> Hi,
>
> I have installed and run OLSR successfully. I also
> got that error before
> with OLSR. The problem is due to using wrong index i
> of a vector (i is
>
> out
>
> of range [0,size_of_vector]). This may happen when
> you delete an element
> of the vector inside the 'for loop' which accesses
> all element of that
> vector.
>
> Regards,
> Viet
>
> Hi,
>
> I have been using the dsr routing implementation
> in Click. I met
> "assertion"
> failed problem before. I fixed it by checking
> the input of the
>
> function. I
>
> suggest you to look into the "vetor' code and
> check when the fail
> happened,
> if "_n" or "i" here is a valid number. There
> might be some situation i
>
> is
>
> out of range [0,_n]. So you might just need to
> check on that to fix
>
> bug.
>
>
> Good luck,
> Zi
>
>
> --
> Zi Feng
> PhD student
> Department of Computer Science and Engineering, UCR
> Network Lab
>
> On Thu, Jan 13, 2011 at 11:57 PM, Bart
> Braem<bart.braem at ua.ac.be
> <mailto:bart.braem at ua.ac.be>>
>
> wrote:
>
>
> Hi,
>
> On 14 Jan 2011, at 03:33, Abhishek Chanda wrote:
>
> I am trying to run the Click
> implementation of OLSR. It did build and
> install successfully, but now when I try
> to run a click script that
>
> has a
>
> FromDevice element, I am getting this error:
> "click: ../include/click/vector.hh:184:
> void*&
> Vector<void*>::operator[](int):
> Assertion `i>=0&& i<_n' failed.
> Aborted”
> What is going wrong?
>
>
> Please use gdb or another debugger to
> provide a stacktrace. I thought
> the
> OLSR implementation we provide on github was
> working, but this could
> point
> to bugs.
>
> best regards,
> Bart
> --
> Bart Braem
> PATS research group - IBBT
> Dept. of Mathematics and Computer Sciences
> University of Antwerp
> Campus Middelheim, G3.27
> Middelheimlaan 1
> B-2020 Antwerpen, Belgium
> Phone: +32 (0)3 265.38.82
> Fax: +32 (0)3 265.37.77
> Web: www.pats.ua.ac.be
> <http://www.pats.ua.ac.be>
>
>
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> <mailto:click at amsterdam.lcs.mit.edu>
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>
>
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> <mailto:click at amsterdam.lcs.mit.edu>
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>
>
> --
>
>
>
>
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu <mailto:click at amsterdam.lcs.mit.edu>
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>
>
>
>
>
>
>
> --
> Abhishek Chanda
More information about the click
mailing list