There is an issue in the testbed-ng branch. If a BANT receives the client, the client stops the route discovery timer and starts an delivery timer. Stopping the route discovery timer basically means:
- Interrupting the corresponding route discovery timer
- Deleting the context object of the route discovery timer
However, interrupting the timer somehow fails resulting in a call to the client which itself calls the handleExpiredRouteDiscovery method. The method tries to access the context object of the expired timer and basically segfaults (since it has been previously deleted).
There is an issue in the
testbed-ngbranch. If a BANT receives the client, the client stops the route discovery timer and starts an delivery timer. Stopping the route discovery timer basically means:However, interrupting the timer somehow fails resulting in a call to the client which itself calls the
handleExpiredRouteDiscoverymethod. The method tries to access the context object of the expired timer and basically segfaults (since it has been previously deleted).