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 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news1.google.com!news.glorb.com!feeder.erje.net!news2.arglkargh.de!news.n-ix.net!news.belwue.de!newsfeed01.sul.t-online.de!t-online.de!goblin2!goblin.stu.neva.ru!fi.sn.net!newsfeed1.tdcnet.fi!news.song.fi!not-for-mail Date: Wed, 15 Jul 2009 21:32:04 +0300 From: Niklas Holsti Organization: Tidorum Ltd User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Asynchronous abort not working in Debian GNAT? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <4a5e20ac$0$6254$4f793bc4@news.tdc.fi> NNTP-Posting-Host: 81.17.205.61 X-Trace: 1247682732 news.tdc.fi 6254 81.17.205.61:55572 X-Complaints-To: abuse@tdcnet.fi Xref: g2news2.google.com comp.lang.ada:7077 Date: 2009-07-15T21:32:04+03:00 List-Id: Under Debian Sarge on Intel, gnat 3.15p, I implemented a time-out for an application using the canonical construct: select delay Time_Out; Error (...); then abort Processing (...); end select; After upgrading to Debian Lenny, FSF GNAT 4.3.2, it appears that this no longer works; instead, Processing completes without being aborted, unless Processing does something that probably invokes scheduling, for example "delay 0.0" or Text_IO output to the console. Running "strace" on the program shows that a SIGABRT is signalled at TIme_Out, but does not abort Processing until Processing does something like delay or console output. The GNAT polling option (-gnatP) does not seem to help. I did not find any Debian bug report on this issue. Has anyone else seen this? Do you know of work-arounds? Other than sprinkling the code with frequent delay statements. -- Niklas Holsti Tidorum Ltd niklas holsti tidorum fi . @ .