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 X-Google-Thread: 103376,c74f051eab6a7903,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-02-06 05:51:29 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!nycmny1-snh1.gtei.net!nycmny1-snf1.gtei.net!news.gtei.net!colt.net!peernews3.colt.net!newsfeed.stueberl.de!fu-berlin.de!uni-berlin.de!7189-cm.able.ES!not-for-mail From: Jano <402450@cepsz.unizar.es> Newsgroups: comp.lang.ada Subject: Gnat/windows specific, exception glich Date: Thu, 6 Feb 2003 14:51:26 +0100 Message-ID: NNTP-Posting-Host: 7189-cm.able.es (212.97.171.89) X-Trace: fu-berlin.de 1044539487 39446722 212.97.171.89 (16 [49872]) X-Newsreader: MicroPlanet Gravity v2.50 Xref: archiver1.google.com comp.lang.ada:33834 Date: 2003-02-06T14:51:26+01:00 List-Id: Hello, I have a curious problem. I'm developing an app using Gnat that uses several DLLs also built with Gnat. The problem is: I have several exception handlers at the various levels in the main procedure. However, when an exception is raised *inside* some proc imported from the DLLs, the app aborts and prints the exception in the console. I suspect that's caused because each DLL has its own runtime, as stated in the user guide. That's somewhat puzzling because there is only one thread/task in execution, so I would expect that any exception would be catched by the handler in the main procedure. The burden that implies is that to prevent program abortion I must place a general exception handler in *each* exported function in the DLLs. Bad enough, I don't want the security model to depend on proper implementation of the DLLs. Currently, I have no idea on how to prevent at all abortion caused by some arbitrary DLL. The DLLs are part of a plugin system. I can't afford to have total failure because a DLL is incorrectly developed. Any ideas? Am I doomed? -- ------------------------- Jano 402450[at]cepsz.unizar.es -------------------------