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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,d790b67e2f1afdc0 X-Google-Attributes: gid103376,public From: "David Botton" Subject: Re: How do I debug Ada DLL's? Date: 1999/06/13 Message-ID: <7k0m86$17k2$1@news.gate.net>#1/1 X-Deja-AN: 489127131 References: <7j6utr$rtq$1@nnrp1.deja.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 X-Complaints-To: abuse@gate.net X-Trace: news.gate.net 929291334 40578 199.227.35.232 (13 Jun 1999 16:28:54 GMT) Organization: CyberGate, Inc. NNTP-Posting-Date: 13 Jun 1999 16:28:54 GMT Newsgroups: comp.lang.ada Date: 1999-06-13T16:28:54+00:00 List-Id: I have debuged DLLs written in GNAT using GDB. Infact, I have debugged and even stepped in to (inproc) COM objects using GDB :) In this case the client and the DLL were both written using GNAT. David Botton Chris Warwick wrote in message ... >In article <7j6utr$rtq$1@nnrp1.deja.com>, marceau@lsec.lete.dnd.ca wrote: >>Has anybody out there debugged dll's in Ada? > >why would you make it a DLL, before you have completely debugged it??? There are times where code needs to be a DLL to start with.