LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Page fault on app build v6.0.2

I'm building a large app >350 Vis including several DLL calls which compiled fine until I moved my entire development environment to another machine (still Win98) and now I'm getting the following page fault on building this into an EXE:

LABVIEW caused an invalid page fault in
module LABVIEW.EXE at 017f:006acb8e.
Registers:
EAX=01325774 CS=017f EIP=006acb8e EFLGS=00010246
EBX=00000034 SS=0187 ESP=00bbf7a8 EBP=00bbf7bc
ECX=4d5c3a43 DS=0187 ESI=01325774 FS=439f
EDX=00022038 ES=0187 EDI=00000000 GS=0000
Bytes at CS:EIP:
8b 31 ff 96 20 02 00 00 5f 5e 5d c3 90 90 90 90
Stack dump:
01325774 00022038 00000000 0002202c 01325774 00bbf7dc 00685f90 01325774 00022038 00000000 01312584 01325774 00000000 00bbf7f8 0065e2c5 01325774

Any
help would be greatly appreciated.
0 Kudos
Message 1 of 3
(2,162 Views)
Can you run your application in VI mode on the new computer? I would also try mass compiling.

I am suspicious of the DLL calls in your app. Did you also move all supporting DLL's with it? There may be version imcompatibility between DLL's on the new machine.

Since its difficult to determine the cause from the 'invalid page fault' message you may have systematically strip down your app and try to build EXE's along the way. Hopefully this will pinpoint the cause.

Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

0 Kudos
Message 2 of 3
(2,162 Views)
Yes, the app runs fine in VI mode on the new system. It has been mass compiled repeatedl.

I believe that the DLLs were copied over completely and in the correct locations as the project runs successfully in VI mode.

Yes, I've even done some of the stripping down and can't locate the problem so it's very curious....
0 Kudos
Message 3 of 3
(2,162 Views)