I agree. The cause is lost comminication of sender. I do not have time to debug this problem now. But it gave me a lot of trouble to debug ospf redistribution problem. In the real time system any process crash is the 1st priority problem.
Li --- On Fri, 12/11/09, Ben Greear <[email protected]> wrote: > From: Ben Greear <[email protected]> > Subject: Re: [Xorp-hackers] xorp_static_routes easy to crash. > To: "Bruce Simpson" <[email protected]> > Cc: "Li Zhao" <[email protected]>, [email protected] > Date: Friday, December 11, 2009, 11:51 AM > On 12/11/2009 08:21 AM, Bruce Simpson > wrote: > > Li Zhao wrote: > >> In many test cases, I found xorp_static_routes is > very easy to crash. It is > >> very timer sensitive. > > > > Known issue... first person to fix it wins! > > > > My favoured approach would be to refactor XrlPFSender > objects to use a > > Boost shared_ptr<XrlPFSender>, and turn Xrl's > embedded XrlPFSender* > > pointer into a weak_ptr<XrlPFSender>. > > I think I already fixed this crash in my tree (or at least > worked around it), > though it's not how Bruce is suggesting... > > At least in the case that I debugged previously, this would > only happen when a sender > lost communication somehow, so the root cause may still > exist and cause troubles. > > Thanks, > Ben > > > -- > Ben Greear <[email protected]> > Candela Technologies Inc http://www.candelatech.com > _______________________________________________ Xorp-hackers mailing list [email protected] http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
