Program too big to fit in memory в windows 7 как исправить

Similar threads

I’m new here. Here’s my problem:

I installed MinGW on my Windows 7 Home Premium 32-bit Netbook with Intel Atom CPU N550, 1.50GHz and 2GB RAM.

Now I made a file named hello.h and tried to compile it via CMD with the following command:
«gcc c:\workspace\c\helloworld\hello.h -o out.exe»

It compiles with no error, but when I try to run out.exe, it gives me following error:
«program too big to fit in memory»

Things I have checked:

• I have added «C:\MinGW\bin» to the Windows PATH Variable
• I have googled for about one hour, but ever since I’m a newbie, I can’t
  really figure out what the problem is.
• I have compiled the same code on my 64-bit machine, compiles
  perfectly, but cannot be run due to 64-bit <-> 16-bit problematic.

I’d really appreciate, if someone could figure out, what the problem is. Btw, here’s my hello.h:

#include <stdio.h>

int main(void){
    printf("Hello, World\n");
}

… That’s it. Thanks for your replies.
Cheers, Boris

By default, files with .h extension are treated as header files by GCC. Normally, header files are not supposed to be fed to the compiler directly. They are supposed to be #included into implementation files.

However, GCC implements a special functionality when it sees a header file being fed to it directly. Specifying an .h file in the command line makes GCC interpret it as a request to generate a pre-compiled header file for that .h file. By using an -o option you forced the compiler to give the resultant pre-compiled header file a specific name out.exe.

Nevertheless, the resultant file is not an executable file, it is a pre-compiled header file. You can open it in a hex editor and see that it begins with gpch, which is a GCC’s pre-compiler header signature. Any attempts to «execute» that file will lead to meaningless results. (This is basically like trying to rename a completely random file to .exe extension and then «running» it.)

answered May 12, 2014 at 1:11

2. Open Computer Properties

3. Navigate to Advanced

4. Click on Environment Variables button

5. Select variable PATH and click the Edit button

6. Append the copied TDM-GCC path at the end. Don’t forget the semicolon.

After all of those steps, hit Ok, Ok, Apply, Ok. And you’re set!

Here’s the result in Command Prompt:

answered Oct 6, 2018 at 16:43