Need help understanding this: Error -1073741819

[awsdert]

Here's my full compiler output:

NPP_EXEC: "Run Make"
NPP_SAVEALL
CD: X:\GitHub\paw\src
Current directory: X:\GitHub\paw\src
make -D CURRENT_DIRECTORY="X:\GitHub\paw\src" -D MINGW="X:\PortableApps\PocketCpp_x64\npp/../mingw"
Process started >>>
make (pid = 5080)
make is suspending for 30 seconds...done sleep(30). Continuing.
../paw64.dll
gcc -shared -mwindows -I"../include" -I"../src" -L"../include" -L"../src" -L"../" "../src/win32/paw.c.o" "../src/win32/shared.c.o" -o "../paw64.dll"
../pawchk64.exe
gcc -mwindows -I"../include" -I"../src" -L"../include" -L"../src" -L"../" ../src/win32/test.c.o -l paw64 -o "../pawchk64.exe"
"../pawchk64.exe"
make: *** [makefile:67: ../pawchk64.exe] Error -1073741819
<<< Process finished. (Exit code 2)
================ READY ================

I'm about to upload the source files here if you need them
Edit: Issue cropped up with my Git Client, having to reinstall give me a few minutes on those files
Edit2: Liked the GUI of Github Desktop better but GitHub4Windows worked better so anyways files are now uploaded

[Salem]

Put -1073741819 into your calculator and convert to hex - you get C0000005.
This is windows generic "access violation".

I suppose it would be better if you could figure out whether it was make, gcc or pawchk64.exe that was crashing.

[awsdert]

I got that much, I was hoping for help on what to look for or perhaps identification of incorrect/missing compile flags (which I suspect is the case). Since it IS reaching as far as compiling the exe I know it can't be a fault with the code or missing files, the only thing I can think of is the flags I'm using, any help is greatly appreciated.

[stahta01]

-l paw64

Is that a space between the "L" and the library name?
If yes, I would try it with no space.

Tim S.

[awsdert]

Didn't make any difference :|

Edit: I even add Load/FreeLibrary into main() to ensure paw32/64.dll was loaded, still no change

[stahta01]

As was already suggested you need to narrow down what is crashing.

The exe that was built, gcc, or make?

Tim S.

[awsdert]

make was use to run the makefile while gcc was used to compile everything else

[stahta01]

make was use to run the makefile while gcc was used to compile everything else

So, you do not know how to compile the program without using make?

If so, I can not help you. Maybe someone else can teach you how to not use make.

Tim S.

[awsdert]

It's not that I can't it's that it's bothersome to repeat the same string over and over when a simple makefile will avoid the (very likely) mistakes I would make from typing those strings (I even made a bunch of typos while writing this) and I see no point to doing it manually unless there is good reason to do so such as needing different flags for different files, in the case of my current project that doesn't apply currently.

[stahta01]

It's not that I can't it's that it's bothersome to repeat the same string over and over when a simple makefile will avoid the (very likely) mistakes I would make from typing those strings (I even made a bunch of typos while writing this) and I see no point to doing it manually unless there is good reason to do so such as needing different flags for different files, in the case of my current project that doesn't apply currently.

I have decided you are not worth my time to try to help; the reason is you do not think its worth your time to try to solve your problem!

Tim S.

[stahta01]

How to Copy and Paste in Command Prompt on Windows 7/10 – iSumsoft

Thought about you saying it is too hard; and, thought you might not know how to paste.

Tim S.

[Salem]

The first thing I would suggest you do is remove the make rule that causes line 13 of your output.

> gcc -mwindows -I"../include" -I"../src" -L"../include" -L"../src" -L"../" ../src/win32/test.c.o -l paw64 -o "../pawchk64.exe"
This compiles your .exe

> "../pawchk64.exe"
This runs your .exe, and it barfs.

This is neither a gcc problem, nor a make problem.

[awsdert]

Of course it compiles the exe, I WANT it to be compiled, how can I test something that is not compiled? As for running it I expected that since I needed to check it is running correctly, don't you lot ever test the code you write? Of course you do otherwise you'd be incompetent and not worth me listening to.

Edit: I didn't say it was a problem with gcc or make just that I suspect my flags are either incorrect or missing some. Ah I should also mention I'm using PocketCPP64 for this.

[awsdert]

As was already suggested you need to narrow down what is crashing.

The exe that was built, gcc, or make?

Tim S.

Does this from the compiler output I provided above not answer your question?

make: *** [makefile:67: ../pawchk64.exe] Error -1073741819

[Salem]

Well apparently, you're far more interested in blaming make or gcc, rather than looking for bugs in YOUR code.

Just try running ../pawchk64.exe and see how far you get.
If it crashes just the same just by typing it on the command line, then you know where the problem is (most likely a PICNIC problem).