View previous topic :: View next topic |
Author |
Message |
AKS
Joined: 19 Mar 2008 Posts: 29
|
Posted: Wed Mar 20, 2019 6:29 pm Post subject: Problems with building an executable |
|
|
I have a program that has been thoroughly debugged. The program compiles successfully, and I get the object files but when I go to build and open the executable I get an error message that it has stopped working. The details show as follows:
Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: smp93.exe
Application Version: 0.0.0.0
Application Timestamp: 5c9274c5
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7c78c
Exception Code: e0434f4d
Exception Offset: 000000000000a49d
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
When I go the the MSDOS window, it says this:
Unhandled Exception: System.TypeInitializationException: The type initializer fo
r 'smp93' threw an exception. ---> System.TypeInitializationException: The type
initializer for 'Salford.Fortran.RTLibrary' threw an exception. ---> System.BadI
mageFormatException: An attempt was made to load a program with an incorrect for
mat. (Exception from HRESULT: 0x8007000B)
at Salford.Fortran.RTLibrary.__com_plus_initialise(Int32 hin)
at Salford.Fortran.RTLibrary.InitLibrary()
--- End of inner exception stack trace ---
at Salford.Fortran.RTLibrary.InitLibrary()
at smp93..cctor()
--- End of inner exception stack trace ---
at smp93.SMP87()
Press RETURN to close window . . .
It worked with the older ftn77 (non windows using leahy fortran compiler) but not this one. I also noticed that the size of the executable is much smaller than it used to be (about 40% smaller) |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7925 Location: Salford, UK
|
Posted: Wed Mar 20, 2019 8:36 pm Post subject: |
|
|
It looks like you are compiling for .NET. Is that what you want? |
|
Back to top |
|
|
AKS
Joined: 19 Mar 2008 Posts: 29
|
Posted: Tue Mar 26, 2019 10:33 pm Post subject: Re: |
|
|
PaulLaidler wrote: | It looks like you are compiling for .NET. Is that what you want? |
No I'm not. I run my batch file and my object files compile and then I make a library out of them, but when I link the library to the main program using slink, it gives me the error
Quote: | Salford exception error
Fail to register registers dialogue procedure |
I hit OK on that pop up and the next message reads
Quote: | Access Violation: The instruction at 004196c8 attempted to read from location 002af20c | and then a bunch of letters and numbers I don't understand.
I have listed below my compile link batch file:
rem PATH =C:\ftn95\BIN;c:\ftn95\lib;C:\DOS
path = c:\users\aks\desktop\old c from Gamma\program files\silverfrost\ftn95
ftn95 AINPUT.FOR
ftn95 AMDPRN.FOR
ftn95 BILGEK.FOR
ftn95 BKLIFT.FOR
ftn95 BRWVSP.FOR
ftn95 CDCOMP.FOR
ftn95 CLIP.FOR
ftn95 COFOUT.FOR
ftn95 COS.FOR
ftn95 CPINTG.FOR
ftn95 CSOLVE.FOR
ftn95 DATE.FOR
ftn95 EDMKSP.FOR
ftn95 EXFOR.FOR
ftn95 FETCH.FOR
ftn95 FIG11.FOR
ftn95 FIG7.FOR
ftn95 FINTSP.FOR
ftn95 FNLIFT.FOR
ftn95 FTWO.FOR
ftn95 GRNFRQ.FOR
ftn95 HLEDDY.FOR
ftn95 HSTAT.FOR
ftn95 HYD2D.FOR
ftn95 INERST.FOR
ftn95 INTRPL.FOR
ftn95 JNWVSP.FOR
ftn95 LRAO.FOR
ftn95 LSCOF.FOR
ftn95 NORMT5.FOR
ftn95 ORGRAO.FOR
ftn95 PADD.fOR
ftn95 PINT.FOR
ftn95 PRAO.FOR
ftn95 PSPLC.FOR
ftn95 PVAL.FOR
ftn95 RAOPHA.FOR
ftn95 RDBASE.FOR
ftn95 RDEDDY.FOR
ftn95 RDLIFT.FOR
ftn95 RDPRIN.FOR
ftn95 RDPelm.FOR
ftn95 REGWAV.FOR
ftn95 REVAL.FOR
ftn95 RLITR.FOR
ftn95 RMSOUT.FOR
ftn95 RPHI2D.FOR
ftn95 RSTITL.FOR
ftn95 SBEDDY.FOR
ftn95 SCB2.FOR
ftn95 SERAB.FOR
ftn95 SERE.FOR
ftn95 SEVMOT.FOR
ftn95 SKLIFT.FOR
rem ftn95 SMP91.FOR
ftn95 smp93-1.for
ftn95 SPFIT.FOR
ftn95 SPINTG.FOR
ftn95 SPLNFT.FOR
ftn95 SPLVAL.FOR
ftn95 T2DAMD.FOR
ftn95 TANAKA.FOR
ftn95 TFNFIT.FOR
ftn95 TRIM.FOR
ftn95 TWODPT.FOR
ftn95 VISC.FOR
ftn95 WAVMAK.FOR
ftn95 WTPELM.FOR
ftn95 ACTFIN.FOR
ftn95 ADRES.FOR
ftn95 ALAG.FOR
ftn95 ALGRNG.FOR
ftn95 AMD.FOR
ftn95 ATAN3.FOR
ftn95 BKEDDY.FOR
ftn95 BMAX.FOR
ftn95 CALRGM.FOR
ftn95 CEVAL.FOR
ftn95 CMINR.FOR
ftn95 CONIWT.FOR
ftn95 CPFIT.FOR
ftn95 CPLVAL.FOR
ftn95 CUBCO2.FOR
ftn95 DKWSLM.FOR
ftn95 EQMOTN.FOR
ftn95 EXPINT.FOR
ftn95 FIG10.FOR
ftn95 FIG56.FOR
ftn95 FIG8.FOR
ftn95 FNEDDY.FOR
ftn95 FNRAO.FOR
ftn95 GENOFS.FOR
ftn95 GRNLOG.FOR
ftn95 HLLIFT.FOR
ftn95 HSTOUT.FOR
ftn95 HYDCAL.FOR
ftn95 INPUT.FOR
ftn95 IRGSEA.FOR
ftn95 LIMIT.FOR
ftn95 LRAOUT.FOR
ftn95 NORML.FOR
ftn95 ORAO.FOR
ftn95 OUTPUT.FOR
ftn95 PDER.FOR
ftn95 PMPY.FOR
ftn95 PRELIM.FOR
ftn95 PSPSC.FOR
ftn95 RAOOUT.FOR
ftn95 RAOPHS.FOR
ftn95 RDCOMP.FOR
ftn95 RDEVAL.FOR
ftn95 READ.FOR
rem ftn95 rdprin.for
ftn95 RELMOT.FOR
ftn95 RLITER.FOR
ftn95 RMS.FOR
ftn95 rmsout.for
ftn95 RMSTOE.FOR
ftn95 RSOLVE.FOR
ftn95 RVSLAT.FOR
ftn95 SBLIFT.FOR
rem ftn95 splfil.for
ftn95 SECT.FOR
ftn95 SERD.FOR
ftn95 SETSEV.FOR
ftn95 SKFRSP.FOR
ftn95 SKNFRC.FOR
ftn95 SOLVE.FOR
ftn95 SPINT2.FOR
ftn95 SPLNAR.FOR
ftn95 SPLNT2.FOR
ftn95 SPPLV2.FOR
ftn95 T3DAMD.FOR
ftn95 TEPEAK.FOR
ftn95 TOE.FOR
ftn95 TRNLAT.FOR
ftn95 VELACC.FOR
ftn95 VUNIT2.FOR
ftn95 WEDEFN.FOR
ftn95 XMSSC.FOR
rem
DEL SMP91.LIB
slim AINPUT.obj /file:smp91.lib
slim SMP91.LIB AMDPRN.obj /file:smp91.lib
slim SMP91.LIB BILGEK.obj /file:smp91.lib
slim SMP91.LIB BKLIFT.obj /file:smp91.lib
slim SMP91.LIB BRWVSP.obj /file:smp91.lib
slim SMP91.LIB CDCOMP.obj /file:smp91.lib
slim SMP91.LIB CLIP.obj /file:smp91.lib
slim SMP91.LIB COFOUT.obj /file:smp91.lib
slim SMP91.LIB COS.obj /file:smp91.lib
slim SMP91.LIB CPINTG.obj /file:smp91.lib
slim SMP91.LIB CSOLVE.obj /file:smp91.lib
slim SMP91.LIB DATE.obj /file:smp91.lib
slim SMP91.LIB EDMKSP.obj |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7925 Location: Salford, UK
|
Posted: Wed Mar 27, 2019 7:36 am Post subject: |
|
|
If you are creating a Win32 application, LIB or DLL then you should be using SLINK and not SLIM. There should be only one SLINK session to do the linking.
You should also be clear about whether you want to build:
1) an application or
2) a DLL or
3) an import LIB or
4) a static LIB.
Each of these require different SLINK commands.
SLIM allows you to create a static Win32 LIB but you can also do this with SLINK. |
|
Back to top |
|
|
|