This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Possible crash when data not sent out a multicast socket for an extended amount of time.

I have a product using the TM4C1294NCPDTI3 where it basically sends out a multicast packet when an I/O line changes. It works every time except in a situation where the I/O line doesn't change for about 2 days.  When it does change after the extended time, the device crashes, then reboots after the watchdog expires. I'm not 100% sure it's the sendTo() call but it seems the most likely since sending the UDP packet is about the only thing the code does in response to the I/O line changing.  I've looked through all of the socket options and don't see any that would intentionally configure this sort of timeout of the socket being functional.  I also suspected one of my tasks was overflowing but all of my stack sizes are stable after an hour or so of run time.   If anyone has an ideas I would appreciate hearing them.  I'll continue to prove it's the sendTo() call that is causing the crash but it does take 2 days for each iteration.

Thanks