Error code: -1073741819

[Vortex]

The IDE can compile C code without issues. It's the linking step causing the issue.

[HellOfMice]

No Problem in Debug mode
OK in Release mode 

[HellOfMice]

I join the project and the hardcopy of my windows and Pelle's versio

[TimoVJL]

The IDE can compile C code without issues. It's the linking step causing the issue.

If pocc.exe works, it is a good thing for us.

[HellOfMice]

I made another test directly under powershell no problem because in my previous tests I launched the console program from POEdit.
I think that W11 R24 has a problem

[Vortex]

How does Pelles IDE executes the linker Polink? If I am not wrong, it must be CreateProcess. Maybe, something changed in this Win32 API function.

[HellOfMice]

Hi Vortex.

In this case one must try directly under powershell with a batch file as you do for your programs

[alderman2]

I join the project and the hardcopy of my windows and Pelle's versio

If your Windows is displayed, you have version 23H2. That version I had no problems with Pelles, only with 24H2 I have problems.

[iwrbc]

The IDE can compile C code without issues. It's the linking step causing the issue.

Interesting. I was working on a project with several source files, and after compilation of each file, the error occurred in my case. So clearly the issue was in the compiler as well.
I went back to 23H2 so I can not test other combinations anymore.
Wilko

[HellOfMice]

Since we meet this error in Pelle's compiler and assembler in my case, it creates errors in NotePad++. I submit a bug report to NotePad++ team. I am asking to myself if I left Pelle's tools for MASM64 or WASM or UASM; I hesitate again. There are tools I don't like in Pelle's and the way Pelle let us falling make me thinking that that could be the best choice. If it is a real bug in POCC or in POASM or in POLINK, it will never be corrected. PO tools are finished.


Philippe RIO

[John Z]

I thought I read somewhere MASM used at least one of Pelles po....exe.  Is that affecting MASM, or was just an option to use?

John Z

[TimoVJL]

masm32 have some Pelles C 6.5032-bit tools, as those still support CV-debug info.

[TimoVJL]

Since we meet this error in Pelle's compiler and assembler in my case, it creates errors in NotePad++. I submit a bug report to NotePad++ team. I am asking to myself if I left Pelle's tools for MASM64 or WASM or UASM; I hesitate again. There are tools I don't like in Pelle's and the way Pelle let us falling make me thinking that that could be the best choice. If it is a real bug in POCC or in POASM or in POLINK, it will never be corrected. PO tools are finished.


Philippe RIO

I can live without Windows 11 24H2, but not without Pelles C 

[HellOfMice]

I used the M option to see if there was a problem with one file other than my source file, but no. It seems that the problem is with the final one. I made tests under powershell and I have not the error code. I just have a problem with a file it does not find. It is just an option in pocc that I have not set I think.

Here is my cmd file:

@echo off
CLS
C:
CD "C:\Users\51966\Documents\# Asm & C #\# Assembleur #\Awpe"
echo *********************
echo *** DEBUG VERSION ***
echo *********************
REM INCLUDE = "C:\Program Files\PellesC\Include\Win;C:\Program Files\PellesC\Include"
REM LIB = -LIBPATH "C:\Program Files\PellesC\Lib\Win64;C:\Program Files\PellesC\Lib"
"C:\Program Files\PellesC\Bin\poasm.exe" -AAMD64 -Zi -Gz -Fo"Asm Library.obj" "Asm Library.asm"
"C:\Program Files\PellesC\Bin\poasm.exe" -AAMD64 -Zi -Gz -Fo"AwPe.obj" "AwPe.asm"
"C:\Program Files\PellesC\Bin\poasm.exe" -AAMD64 -Zi -Gz -Fo"Display Data Directories.obj" "Display Data Directories.asm"
"C:\Program Files\PellesC\Bin\poasm.exe" -AAMD64 -Zi -Gz -Fo"PE Toolkit.obj" "PE Toolkit.asm"
"C:\Program Files\PellesC\Bin\pocc.exe" -Tx64-coff -std:C2X -Zi -Ot -Ob1 "Create_DlgDataDirectories.c" -I"C:\Program Files\PellesC\Include\Win;C:\Program Files\PellesC\Include" -fp:precise -W1 -Gr -Ze -Zx -GX -J -Fo"Create_DlgDataDirectories.obj"
"C:\Program Files\PellesC\Bin\porc.exe" -N -r "Awpe.rc" -Fo"Awpe.res"
"C:\Program Files\PellesC\Bin\polink.exe" -LIBPATH:"C:\Program Files\PellesC\Lib\Win64;C:\Program Files\PellesC\Lib" -machine:x64 -debug -debugtype:po -subsystem:windows -map -release -largeaddressaware kernel32.lib user32.lib gdi32.lib comctl32.lib comdlg32.lib advapi32.lib delayimp64.lib -out:"Awpe.exe" "Asm Library.obj" "AwPe.obj" "Awpe.res" "Create_DlgDataDirectories.obj" "Display Data Directories.obj" "PE Toolkit.obj"
echo ***************************
echo *** PROJET READY TO RUN ***
echo ***************************
pause

and the result is joint to my post

When I use the debugger it creates problems with NotePad++ and others, I already have lost many files.
I hate Microsoft tools, with Pelle's tools what I like is to have all what I need but who will make corrections?

[TimoVJL]

When I use the debugger it creates problems with NotePad++ and others, I already have lost many files.

So files are not closed normally, if exceptions occur ?