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.236.126.103 with SMTP id a67mr13262770yhi.4.1408305095178; Sun, 17 Aug 2014 12:51:35 -0700 (PDT) X-Received: by 10.50.43.196 with SMTP id y4mr793212igl.13.1408305095077; Sun, 17 Aug 2014 12:51:35 -0700 (PDT) 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!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!i13no681889qae.1!news-out.google.com!aw9ni1931igc.0!nntp.google.com!r2no1744007igi.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sun, 17 Aug 2014 12:51:34 -0700 (PDT) In-Reply-To: <9e4585b7-2d01-4877-a24c-3fd23625fbff@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=108.69.213.73; posting-account=jTyM8goAAADJ35CkjDrbWN1e-B_W_S9y NNTP-Posting-Host: 108.69.213.73 References: <9e4585b7-2d01-4877-a24c-3fd23625fbff@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Trouble with Timers on the ARM From: Mike Silva Injection-Date: Sun, 17 Aug 2014 19:51:35 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Received-Bytes: 2030 X-Received-Body-CRC: 4184565570 Xref: news.eternal-september.org comp.lang.ada:21799 Date: 2014-08-17T12:51:34-07:00 List-Id: On Saturday, August 16, 2014 9:43:53 PM UTC-7, William Thomas wrote: > > Thanks Mike, > > > > I got the last chance handler to print out the Null terminated string returned at address along with the line number. Sure enough I received the same message coming from System.Tasking.Protected_Objects. > > > > It turns out that I had to set the protected object's priority to System.Max_Interrupt_Priority in order for the timer to work properly. > > > > I would imagine its because the Callback is being called back by something that was being executed as a result of some processor timer which I believe would have to be coming in at Max_Interrupt_Priority. > > > > Thanks for the help. > > > > Bill Great, Bill. What a useful tool! Mike