[Xorp-users] Bugs? recursive malloc, fib2mrib doesn't update nexthop vif, and PIM RP never initiates a Register-Stop

[Pavlin Radoslavov]

> On 8/15/06, Pavlin Radoslavov <pavlin at icir.org> wrote:
> > > I am using XORP 1.3-Release for PIM-SMv6 and Zebra 0.95 for unicast
> > > routing on FreeBSD 6.1.
> > > The situations are:
> > > 1. xorpsh sometimes issues recursive malloc calls, causing segmentation fault.
> >
> > Is the problem reproducible?
> > If "yes", can you provide detailed instructions how to trigger it.
> > If "no", can you send a backtrace of the coredump.
> It sometimes happened after I gave "show pim6 join"  or "show pim6 mrib"
> 
> the XORP was not compiled with -ggdb on, so the backtrace after the
> "show pim6 join" is
> #0  0x284d4363 in kill () from /lib/libc.so.6
> (gdb) bt
> #0  0x284d4363 in kill () from /lib/libc.so.6
> #1  0x284d4300 in raise () from /lib/libc.so.6
> #2  0x284d3014 in abort () from /lib/libc.so.6
> #3  0x284794d3 in _UTF8_init () from /lib/libc.so.6
> #4  0xbfbfed98 in ?? ()
> #5  0x284da4c9 in sys_nsig () from /lib/libc.so.6
> #6  0x284da3d7 in sys_nsig () from /lib/libc.so.6
> #7  0x284da49b in sys_nsig () from /lib/libc.so.6
> #8  0x00000000 in ?? ()
> #9  0x284e4508 in ?? () from /lib/libc.so.6
> #10 0xbfbec2c8 in ?? ()
> #11 0x28479501 in _UTF8_init () from /lib/libc.so.6
> #12 0x284e4508 in ?? () from /lib/libc.so.6
> #13 0x08230564 in vtable for __cxxabiv1::__class_type_info ()
> #14 0xbfbec378 in ?? ()
> #15 0x2847a588 in _UTF8_init () from /lib/libc.so.6
> #16 0x00000020 in ?? ()
> Previous frame inner to this frame (corrupt stack?)

Thank you for the update. It is not sufficient to point the source
of the failure, but seems consistent with another backtrace I got
this morning from Mark Handley.

Anyway, I just committed some code that hopefully will print some
debug info if this happens again:

Revision  Changes                                Path
1.27      +13 -4;  commitid: 14b3f44e4f1357ea6;  xorp/libxorp/run_command.cc

Please update this file (only) with the changes and next time it
happens please send me printed messages.


> > > 2. XORP doesn't update its nexthop vif on multicast routing table If
> > > Zebra updates a routing entry.
> > >     show route table ipv6 multicast fib2mrib shows that the nexthop
> > > vif is not  changed even though the nexthop address is.
> > >   I am not sure whether this problem is intermittent or not.
> >
> > Can you trigger the same problem by using userland commands like
> > "route delete" and "route add". If "yes", could you provide the
> > sequence of those commands.
> 
> Here's the snippet of the ndp command on my router
> fe80::2e0:81ff:fe20:afc2%fxp0        0:e0:81:20:af:c2    fxp0 16h26m32s S R
> fe80::207:e9ff:fe05:ba6f%fxp1        0:7:e9:5:ba:6f      fxp1 17s       R R
> 
> a. after
> route -n add -inet6 A:B:C:D::/64 fe80::2e0:81ff:fe20:afc2%fxp0
> 
> show pim6 mrib shows
> A:B:C:D::/64 fe80::2e0:81ff:fe20:afc2 fxp0    0               254  65535
> 
> b. after
> route -n change -inet6 A:B:C:D::/64 fe80::207:e9ff:fe05:ba6f%fxp1
> show pim6 mrib shows
> A:B:C:D::/64 fe80::207:e9ff:fe05:ba6f fxp0    0               254  65535
> 
> c. deleting the A:B:C:D::/64 and then
> route -n add -inet6 A:B:C:D::/64 fe80::207:e9ff:fe05:ba6f%fxp1
> gives the same result
> 
> show pim6 mrib shows
> A:B:C:D::/64 fe80::207:e9ff:fe05:ba6f fxp0    0               254  65535

Thank you for the info. I will look into that.

Pavlin