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.42.123.139 with SMTP id s11mr9517883icr.15.1389695673779; Tue, 14 Jan 2014 02:34:33 -0800 (PST) X-Received: by 10.49.122.42 with SMTP id lp10mr13794qeb.17.1389695673748; Tue, 14 Jan 2014 02:34:33 -0800 (PST) Path: border1.nntp.dca3.giganews.com!backlog3.nntp.dca3.giganews.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!6no9589288qao.1!news-out.google.com!gg4ni2493qab.0!nntp.google.com!p15no13941311qaj.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 14 Jan 2014 02:34:33 -0800 (PST) In-Reply-To: <8e6d38d4-4790-4912-af78-f67b9621e6d3@googlegroups.com> 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 References: <8e6d38d4-4790-4912-af78-f67b9621e6d3@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: adasockets on raspbian (armhf) and debian (intel32) From: tonyg Injection-Date: Tue, 14 Jan 2014 10:34:33 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Original-Bytes: 2456 Xref: number.nntp.dca.giganews.com comp.lang.ada:184415 Date: 2014-01-14T02:34:33-08:00 List-Id: On Monday, 13 January 2014 15:07:01 UTC, tonyg wrote: > 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? Problem was the latest raspbian distribution and something to do with sockets. Ealier distributions than the one released on 2013-12-20 work fine but this does not for some reason.