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=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.68.135.99 with SMTP id pr3mr2516880pbb.9.1412695633483; Tue, 07 Oct 2014 08:27:13 -0700 (PDT) X-Received: by 10.140.96.54 with SMTP id j51mr15819qge.13.1412695633348; Tue, 07 Oct 2014 08:27:13 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!feeder.erje.net!eu.feeder.erje.net!news2.arglkargh.de!news.glorb.com!uq10no5784892igb.0!news-out.google.com!bc9ni17237igb.0!nntp.google.com!h18no2725438igc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 7 Oct 2014 08:27:13 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=50.138.108.48; posting-account=yiWntAoAAAC1KqC_shmxJYv07B9l6LNU NNTP-Posting-Host: 50.138.108.48 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <35415309-308c-43ce-b219-fc1e8e9d62af@googlegroups.com> Subject: Re: gnoga: SIGSEGV in aws.net.websocket.send() when exiting application From: David Botton Injection-Date: Tue, 07 Oct 2014 15:27:13 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: news.eternal-september.org comp.lang.ada:22177 Date: 2014-10-07T08:27:13-07:00 List-Id: > press "Exit Application" in any of the tutorials. Is this currently expected? Not per se, I haven't seen it, but anything is possible. It has only been tested on debian and Mac OS X to any large extent. Trying to Exit out of a heavily multi tasking environment cleanly is not easy especially where there are some quirks in AWS and GNAT with ATC. I'll try and see what your error digs up on my search, but just give me a bit of patience on it for a few more weeks then I'll try and fire up a few VMs if needed to figure out where that is happening. It does look to me though like it may be a race condition with Gnoga trying to communicate to the browser after the socket connection is lost or in the middle of closing. So I will reanalyze the code there. David Botton