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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII X-Google-Thread: 103376,47bb60b4d120639a X-Google-Attributes: gid103376,public From: Steve Quinlan Subject: Re: exception Date: 1998/11/03 Message-ID: <363F5BD6.1A58@lmco.com>#1/1 X-Deja-AN: 408028343 Content-Transfer-Encoding: 8bit References: <363992D5.643F343E@biha01.ehu.es> Content-Type: text/plain; charset=iso-8859-1 Organization: Lockheed-Martin Mime-Version: 1.0 Reply-To: steven.quinlan@lmco.com Newsgroups: comp.lang.ada Date: 1998-11-03T00:00:00+00:00 List-Id: Pablo Campo wrote: > > I am a programmer of ADA and I use the Alsys Active ADA envirotment > version 5.3 > > I am making a proyect full of tasking and interrupts (for example I > manage the clock interrupt) and my problem is that my program breaks > down in execution time and the only information I recive is "Program > terminated. Unhandled exception". > Yesterday, I spent all the morning handling exceptions in all tasks and > subprograms but the result was the same. > �What can I do for obtain more information of the problem? > > Nacho - A spanish enginier student. I don't understand how people can use some of these implementations which make it so hard to figure out where an exception came from unless you are in a debugger. OCS and Aonix for example dump out the exception and a traceback in human readable format (unit/line #) to stdout if a program dies with an unhandled exception. That symbol table is a small price to pay for the ability to do problem determination. Best I can suggest is: Does that environment come with a debugger that you can run the application under? If you've got hanlders in all the tasks and it's still dying, maybe it's happening at elaboration outside the scope of the task body handlers. You'd need a debugger that is capable of breaking on exceptions during elaboration.