BUG: Access Violation Calling Exported Subroutine in DLLLast reviewed: April 12, 1996Article ID: Q149746 |
The information in this article applies to:
SYMPTOMSWhen you use the !MS$ATTRIBUTES DLLEXPORT attribute to export a DLL's subroutine, and call that subroutine from another subroutine within the same DLL it causes the following Access Violation:
The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "written" RESOLUTIONIf you need to call an exported subroutine in a DLL, you should put this code into a non-exported helper subroutine and have the exported subroutine call the non-exported helper subroutine.
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
Steps to Reproduce Problem
Sample Code to Illustrate Problem
MAIN! filename: main.for ! Compile options needed: none
program fortapp interface subroutine thesub() !ms$attributes dllimport, stdcall :: thesub end subroutine end interface call thesub() end program fortapp DLL! filename: sub.for ! Compile options needed: /LD
subroutine thesub() !ms$attributes dllexport, stdcall :: thesub interface subroutine othersub() !ms$attributes dllexport, stdcall :: othersub end subroutine othersub end interface call othersub() end subroutine subroutine othersub() !ms$attributes dllexport, stdcall :: othersub end subroutine |
Additional reference words: 4.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |