[Xorp-hackers] About timeout in Debug.

[Atanu Ghosh]

Hi,

XORP needs to track the state of its processes. Part of this tracking
involves exchanging keepalive messages between the FINDER (a component
in the RTRMGR) and all the other processes. If the RTRMGR is single
stepped using a debugger then the keepalive messages cannot be
exchanged, hence the problem that you are seeing.

This is a common problem when attempting to debug a procss that is
communicating with another process. There is no simple way to avoid the
problem. If by using a debugger you stop the RTRMGR from running for too
long the system will fail. If you understand this then you can set
breakpoints debug the piece of interest and then restart XORP.

    Atanu.

>>>>> "eshe168" == eshe168  <eshe168 at gmail.com> writes:

    eshe168> Hi, all When I use gdb to debug a process in the Debian, I
    eshe168> found there are some timeout information in
    eshe168> xorp_rtrmgr. Then I can not go on debuging the process.
    eshe168> Could you give me a clue to avoid it.

    eshe168> -- Best Regard Xiaoshuai Yang

    eshe168> _______________________________________________
    eshe168> Xorp-hackers mailing list Xorp-hackers at icir.org
    eshe168> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers