On Tue, Sep 11, 2012 at 10:29 AM, Adrian Chadd <adr...@freebsd.org> wrote: > On 11 September 2012 09:01, Dominic Blais <dbl...@interplex.ca> wrote: >> I could do something about the route monitor but not the fstat | grep >> route... I mean, I would have to run it in a loop endlessly until the bug >> happens... Even with it, it's not even sure I would catch it... > > The route monitor is a good idea. It should tell us whether it's from > some tool/program/network event sending a routing table update, or > whether it's just plain memory corruption.
Could this be http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=226120&r2=226224&pathrev=226331 _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
