Lazarus Release 2.2.2

[RadDeveloper]

Hi Lazarus Team!

Here is the bug in this version. Here the steps: Launch Lazarus IDE, Click Project -> View Project Source, then close project1.lpr page, then again Click Project -> View Project Source, then the source page appears to be blank (no project code inside), and cannot compile a project.

Thanks.

[Handoko]

I confirm what RadDeveloper said is reproducible on Lazarus 2.2.2 Linux GTK2.

But that only happens on new project, so the steps to produce the issue are:
1. Start Lazarus
2. File > New > Project > Application > OK
3. Project > View Project Source
4. Close the project1.lpr tab on the Source Editor
5. Project > View Project Source

[JuhaManninen]

It seems to be reported :
 https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39745

[RadDeveloper]

Cannot Debug Win32/Release Application in Lazarus IDE

Reproduction Steps:
1. Launch Lazarus IDE.
2. On default project go to Options for Project: project1
3. In Config and Targets Build modes [Release]
4. Target OS (-T) [Win32], Target CPU family (-P) [i386], Target processor (-Cp) [(Default)]
5. Click Run(F9)...
Error on project1.exe has stopped working. Execution stopped with exit-code 14100065445 ($540BE425)

I previous version this never happen

[dseligo]

Cannot Debug Win32/Release Application in Lazarus IDE

Is your Lazarus installation 64 bit or 32 bit?
What debugger you use, FpDebug or GDB (Project/Project options/Project options/Debugger)?

[jipété]

I confirm what RadDeveloper said is reproducible on Lazarus 2.2.2 Linux GTK2.

Also in old 2.2.0.

[RadDeveloper]

Cannot Debug Win32/Release Application in Lazarus IDE

Is your Lazarus installation 64 bit or 32 bit?
What debugger you use, FpDebug or GDB (Project/Project options/Project options/Debugger)?

Thank you for the reply.
GNU debugger(dbg.exe) falls in the error above I mentioned.
So workaround:
Replace the path with the placeholders e.g
..\Lazarus\mingw\i386-win32\bin\gdb.exe
to
$(LazarusDir)\mingw\$(TargetCPU)-$(TargetOS)\bin\gdb.exe

Now it's working :-)

[dseligo]

Cannot Debug Win32/Release Application in Lazarus IDE

Is your Lazarus installation 64 bit or 32 bit?
What debugger you use, FpDebug or GDB (Project/Project options/Project options/Debugger)?

Thank you for the reply.
GNU debugger(dbg.exe) falls in the error above I mentioned.

You probably don't have 32-bit gdb installed (under Lazarus install directory\mingw, 32-bit in i386-win32\bin\gdb.exe and 64-bit in x86_64-win64\bin\gdb.exe).

[Martin_fr]

Or your app depends on some dll, that you did not put in the new install?

Execution stopped with exit-code

This usually means that your app was started [(1)] (and for that you must have some debugger (if your setting is gdb, then some gdb.exe)), and your app did then quit

[(1)] The exe file was opened by the OS, but it may (or may not) have failed before any code was executed.

- This could be, that the IDE config is hard coded to the 64 bit debugger (though IIRC that causes a diff error).

- Or it could be, that the OS failed to load dependencies.

- Or it could be that your Anti-Virus killed the process.

[RadDeveloper]

Cannot Debug Win32/Release Application in Lazarus IDE

Is your Lazarus installation 64 bit or 32 bit?
What debugger you use, FpDebug or GDB (Project/Project options/Project options/Debugger)?

Thank you for the reply.
GNU debugger(dbg.exe) falls in the error above I mentioned.

You probably don't have 32-bit gdb installed (under Lazarus install directory\mingw, 32-bit in i386-win32\bin\gdb.exe and 64-bit in x86_64-win64\bin\gdb.exe).

Yes I do have 64-bit installed on Windows, plus FPC addon. Seems like correct path with placeholders included were not edited since out of box installation, so I had to put them manually.

[RadDeveloper]

Or your app depends on some dll, that you did not put in the new install?

Execution stopped with exit-code

This usually means that your app was started [(1)] (and for that you must have some debugger (if your setting is gdb, then some gdb.exe)), and your app did then quit

[(1)] The exe file was opened by the OS, but it may (or may not) have failed before any code was executed.

- This could be, that the IDE config is hard coded to the 64 bit debugger (though IIRC that causes a diff error).

- Or it could be, that the OS failed to load dependencies.

- Or it could be that your Anti-Virus killed the process.

No, it's blank TForm 32 bit app. AV is off.

[RadDeveloper]

I suspect that 64 bit debugger tried to debug 32 bit app.

[circular]

Hi! It seems the binaries have not been made for MacOs 32bit:
https://sourceforge.net/projects/lazarus/files/Lazarus%20Mac%20OS%20X%20i386/Lazarus%202.2.2/

I've tried to compile Lazarus 2.2.2 and 2.2.0 using Lazarus 2.0.12 but without success.

In the folder for 2.2RC1, the files does not seem to match:
https://sourceforge.net/projects/lazarus/files/Lazarus%20Mac%20OS%20X%20i386/Lazarus%202.2RC1/

There seem to be FPC for 64bit and Lazarus 2.0.12 for 64bit.

Are there instructions on how to make those files?

[lainz]

Try using fpcupdeluxe