From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.182.66.73 with SMTP id d9mr9283310obt.8.1389625621206; Mon, 13 Jan 2014 07:07:01 -0800 (PST) X-Received: by 10.49.48.105 with SMTP id k9mr436473qen.1.1389625621167; Mon, 13 Jan 2014 07:07:01 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!eu.feeder.erje.net!feeder.erje.net!us.feeder.erje.net!news.ripco.com!news.glorb.com!p15no12547817qaj.0!news-out.google.com!fv6ni2549qab.1!nntp.google.com!p15no12547813qaj.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 13 Jan 2014 07:07:01 -0800 (PST) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=195.58.145.51; posting-account=28F2IwkAAACL1Z5nRC-dE7zuvWdbWC7P NNTP-Posting-Host: 195.58.145.51 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <8e6d38d4-4790-4912-af78-f67b9621e6d3@googlegroups.com> Subject: adasockets on raspbian (armhf) and debian (intel32) From: tonyg Injection-Date: Mon, 13 Jan 2014 15:07:01 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: news.eternal-september.org comp.lang.ada:18162 Date: 2014-01-13T07:07:01-08:00 List-Id: I am using some identical ada/ adasocket code on the raspberry pi and intel. I compile for each on that architecture. Btw I have checked with NMAP to make sure ports are free and working. A socket successfully binds / listens and connects on intel but when I tried this on the latest version of raspbian it gives this error through strace ********** Sockets_Setup_Task: Listening for test harness on port 18010 ) = -1 ETIMEDOUT (Connection timed out) gettimeofday({1389622632, 627619}, NULL) = 0 futex(0x63f318, FUTEX_WAKE_PRIVATE, 1) = 0 exit_group(0) *************** It should also raise an exception rather than bombing out to the command line. I did encounter a slightly similar problem when sending information when it bombed out, in that case though I changed a value in the c_send of adasockets to include a value MSG_NOSIGNL and then it let the exceptions handle things.... Has anyone any ideas on this?