Crash in OTBR related to SRP #2519
Comments
|
Thanks, @agners. Based on my analysis, this appears to be a platform UDP issue and not related to SRP client itself. I assume The assertion is happening in Error Udp::Open(SocketHandle &aSocket, ReceiveHandler aHandler, void *aContext)
{
Error error = kErrorNone;
OT_ASSERT(!IsOpen(aSocket));
aSocket.Clear();
aSocket.mHandler = aHandler;
aSocket.mContext = aContext;
...The if (IsRunning())
{
VerifyOrExit((GetServerAddress() != serverSockAddr) || shouldRestart);
Stop(kRequesterAuto, kResetRetryInterval);
}
...
IgnoreError(Start(serverSockAddr, kRequesterAuto));The Error Udp::Close(SocketHandle &aSocket)
{
Error error = kErrorNone;
VerifyOrExit(IsOpen(aSocket));
#if OPENTHREAD_CONFIG_PLATFORM_UDP_ENABLE
error = otPlatUdpClose(&aSocket);
#endif
SuccessOrExit(error);
RemoveSocket(aSocket);
aSocket.GetSockName().Clear();
aSocket.GetPeerName().Clear();
exit:
return error;
}My suggestion is to investigate the |
|
I'm using OTBR as Docker container with the same hardware (EFR32MG21) and run into the same error I think: i can provide a full log if needed? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug A clear and concise description of what the bug is.
I've encountered a crash using a relatively recent commit ff7227e. It coincided with the shutdown of another OTBR on the same network (this might be by chance, but the timing is very suspicious). This has been observed with the Home Assistant OpenThread Border Router add-on 2.11.0.
To Reproduce Information to reproduce the behavior, including:
Expected behavior A clear and concise description of what you expected to happen.
Console/log output If applicable, add console/log output to help explain your problem.
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: