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,6ae109b8af68b4ac X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-01-10 15:20:09 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!peer1-sjc1.usenetserver.com!usenetserver.com!nf3.bellglobal.com!border1.nntp.aus1.giganews.com!nntp.giganews.com!nntp3.aus1.giganews.com!bin3.nnrp.aus1.giganews.com.POSTED!news.clear.net.nz From: Craig Carey Newsgroups: comp.lang.ada Subject: Re: Summary: GNAT and a very foreign DLL Message-ID: References: X-Newsreader: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Organization: Customer of Mercury Telecommunications Ltd Cache-Post-Path: localhost!unknown@tnt1-230.quicksilver.net.nz X-Cache: nntpcache 2.4.0b3 (see http://www.nntpcache.org/) X-Original-NNTP-Posting-Host: drone5-svc-skyt.qsi.net.nz X-Original-Trace: 11 Jan 2002 12:19:49 +1300, drone5-svc-skyt.qsi.net.nz NNTP-Posting-Date: Thu, 10 Jan 2002 17:19:52 CST X-Trace: sv3-nYwrCNV1/w1f3s81Bl/24IhjDvHrKFuQ88Yb4w+bw5LLaqIpwMEs/RLdzBEpzYUJoskQI0m4uTv4/pS!r0+ue8P/ja0Ly+XH9pwLZnpnLubtC23ntk+YgrD3dfKa/ZmZ1MPA+teX0PiWCYCwFCuPGP7htSxF!SzRiSQ== X-Complaints-To: abuse@GigaNews.Com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-Info: Please be sure to forward a copy of ALL headers X-Abuse-Info: Otherwise we will be unable to process your complaint properly Date: Thu, 10 Jan 2002 23:19:53 GMT Xref: archiver1.google.com comp.lang.ada:18747 Date: 2002-01-10T23:19:53+00:00 List-Id: On Wed, 9 Jan 2002 23:19:53 +0300 (MSK), "Alexandre E. Kopilovitch" wrote: ... > The problem appears to be with the combination of the call convention and >the names of the DLL's entry points: the call convention is surely Stdcall, >but the entry point names do not contain usual suffixes "@nn" - they look as >common C identifiers. When linking in Windows NT DLLs the gnatdll -k option could be needed. >[A] way to specify within an Ada program _any_ name for a DLL's entry >point, regardless of a call convention? The definition file can contain something like this: EXPORTS = abc@4=abc def=_def@4 That could be useful if another compiler is used. >Therefore I just sent to report@gnat.com the - Here is a question. (I did not see answers to these questions in the GNAT 3.13p documents.) How can GNAT DLLs that are called from Delphi, be debugged ?. Apart from use of TCP sockets there can be 2 options including these * Win32 OutputDebugString(string) can be used. What is a good way to capture those strings?. Something from the free Microsoft SDK or something else?. What software is used. * DOS console Window and CreateProcess. (There is an example of a call to that Win32 routine in Mr Obry's Posix library. Has anybody got an example where the thread owning the MSDOS console of a DLL, is an Ada task?. Craig Carey