I have found the problem and fixed it. When the socket is created it needs to be TCP. However when getprotobyname(_sName) is called in the XPCGetProtocol class to lookup the correct protocol number in /etc/protocols it returns the value of the previous time it was called, which was when a UDP socket was setup.
To fix it I simply called the function twice, the second time it returns the correct value. I am not sure why it would return incorrect the first time but this works! On Tuesday, 11 March 2014 23:21:08 UTC+10:30, haeusler...@gmail.com wrote: > > Ok so after much debugging I have found that when the Listen thread socket > is started it starts as a UDP socket (determined using lsof) when it should > be a TCP socket. What would cause this? > > On Wednesday, 5 March 2014 20:32:54 UTC+10:30, haeusler...@gmail.comwrote: >> >> I managed to get it to work in single threaded mode. Has any one had any >> issues with threads with the BBB? >> >> On Wednesday, 5 March 2014 18:58:42 UTC+10:30, haeusler...@gmail.comwrote: >>> >>> I am attempting to run >>> MOOS-IvP<http://oceanai.mit.edu/moos-ivp/pmwiki/pmwiki.php?n=Main.HomePage>on >>> a Beaglebone Black >>> >>> On attempting to run the MOOS database it continuously throws the >>> exception >>> >>> "Exception Thrown in listen loop: Error Listening To Socket. Operation >>> not supported" >>> >>> This software runs on a Raspberry Pi >>> >>> Any ideas what might be the issue? >>> >> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
