Ada call from vc++

Ada call from vc++

[Matthias]

Hi all,

we have an c++-application that includes a dll with adacode. Another
c++-application starts this app with CreateProcess(...). After starting
the c++-app the following error comes up:
"Program terminated by an exception propagated out of the main
subprogram. Exception raised: ADA.IO_EXCEPTIONS.USE_ERROR. Executable
name... EIP EBP..."
If we start the c++-app with the adacode dll manually there is no error
message shown.
Somebody knows about this problem?

Matthias

Re: Ada call from vc++

[James Alan Farrell]

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

Matthias wrote:
> Hi all,
> 
> we have an c++-application that includes a dll with adacode. Another
> c++-application starts this app with CreateProcess(...). After starting
> the c++-app the following error comes up:
> "Program terminated by an exception propagated out of the main
> subprogram. Exception raised: ADA.IO_EXCEPTIONS.USE_ERROR. Executable
> name... EIP EBP..."
> If we start the c++-app with the adacode dll manually there is no error
> message shown.
> Somebody knows about this problem?
> 
> Matthias
> 

What Ada compiler did you use to make the DLL?

If it is gnat, then there is a function ada_init() that must be called 
from c++.

James

[-- Attachment #2: jfarrell.vcf --]
[-- Type: text/x-vcard, Size: 88 bytes --]

begin:vcard
fn:James Alan Farrell
n:Farrell;James
org:GrammaTech
version:2.1
end:vcard

Re: Ada call from vc++

[Björn Persson]

Matthias wrote:
> we have an c++-application that includes a dll with adacode. Another
> c++-application starts this app with CreateProcess(...). After starting
> the c++-app the following error comes up:
> "Program terminated by an exception propagated out of the main
> subprogram. Exception raised: ADA.IO_EXCEPTIONS.USE_ERROR. Executable
> name... EIP EBP..."
> If we start the c++-app with the adacode dll manually there is no error
> message shown.

The RM says: "The exception Use_Error is propagated if an operation is 
attempted that is not possible for reasons that depend on 
characteristics of the external file."

So you'll have to think of things like: Are there any differences in 
which files the DLL tries to access? Does the program get the same 
standard in, standard out and standard error files in both cases? Any 
parameters that might change how it operates on the files?

If you have the source code it'll help you a lot if you can get a stack 
trace and see where the exception comes from.

-- 
Bj�rn Persson                              PGP key A88682FD
                    omb jor ers @sv ge.
                    r o.b n.p son eri nu