GPF in PBDLL 6.0

[Iain Johnstone]

I have started getting GPF's in PBDLL6 on compilation of a program. Firstly the Windows white box appears saying that there is 'an error in the program...'(PBDLL) - Clicking on Close brings up a PBdll message box saying there is an illegal operation (GPF in PBDLL.EXE 0003:0000ee92). Closing this box brings up the compiler results box with the normal program details.

The source code is 542880 bytes, and the disc image is 810496. There are 13 INC files.

I can avoid all this by removing a small amount of source code (which contains no errors). Also, the compiler seems to remember a previous code error, even though this has been corrected and the file saved repeatedly. Has the program been compiled correctly?

I have tried this on two machines, with the same result. Have I hit a limit?

Over to you Tech Support!

Iain Johnstone

------------------

[Eric Pearson]

Are you using the PB IDE or an external editor?

-- Eric


------------------
Perfect Sync: Perfect Sync Development Tools
Email: mailto:[email protected][email protected]</A>

[Iain Johnstone]

Eric:
I am using the PB IDE

Further work
1) the program has not compiled following the error messages
2) The compiler seems to be looking in the log file and reporting the previous error. Deleting the log file gives an empty error message box, and copying a backup log file brings up the concluding message from that, which makes it look as if the file had actually compiled when it has not.
3) Breaking the INC files up into smaller units has not made any difference

Iain Johnstone

------------------

[Lance Edmonds]

It is possible that PBDLL.EXE could be running out of memory during compilation, but it *should* tell you in that case. PBDLL.EXE is actually a 16-bit application, so it is limited to 16Mb of RAM, and depending on the O/S you are using, will share this 16Mb region with other 16-bit processes that are running at the same time...

In general, NT/2000 will provide the greatest amount of memory to the compiler, as compared to 95/98/ME.

*Assuming* that this is actually what is happening, you could try splitting the code down into two or more pieces, and redevelop the app as an EXE and at least one DLL.

Otherwise, submit the code to Tech Support (along with your PowerBASIC serial number) and we'll take a quick look to see if it is a memory problem, or some other type of problem.

------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>