Lazarus

Announcements => Lazarus => Topic started by: mattias on May 19, 2022, 09:26:08 am

Title: Lazarus Release 2.2.2
Post by: mattias on May 19, 2022, 09:26:08 am
The Lazarus team is glad to announce the release of Lazarus 2.2.2.

This is a bugfix release and was built with FPC 3.2.2.

Here is the list of changes for Lazarus and Free Pascal:
http://wiki.lazarus.freepascal.org/Lazarus_2.2.0_release_notes
http://wiki.lazarus.freepascal.org/User_Changes_3.2.2

Here is the list of fixes for Lazarus 2.2.x:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/commits/fixes_2_2

The release is available for download on SourceForge:
http://sourceforge.net/projects/lazarus/files/

Choose your CPU, OS, distro and then the "Lazarus 2.2.2" directory.

Checksums for the SourceForge files:
https://www.lazarus-ide.org/index.php?page=checksums#2_2_2

Minimum requirements:

Windows:
   2k, XP, Vista, 7, 8, 8.1 and 10, 32 or 64bit.

FreeBSD/Linux:
   gtk 2.24 for gtk2, qt4.5 for qt, qt5.6 for qt5, 32 or 64bit.

Mac OS X:
   Cocoa (64bit) 10.12 to 12.3, Carbon (32bit) 10.5 to 10.14, qt and  qt5 (32 or 64bit).

The gitlab page:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/tree/lazarus_2_2_2

For people who are blocked by SF, the Lazarus releases from SourceForge are mirrored at:ftp://ftp.freepascal.org/pub/lazarus/releases/
Title: Re: Lazarus Release 2.2.2
Post by: loaded on May 19, 2022, 10:09:41 am
Many thanks to the lazarus developers. :)
Title: Re: Lazarus Release 2.2.2
Post by: Zvoni on May 19, 2022, 10:20:06 am
Quick question: Is it still the "official" recommendation, to use the 32-Bit Version of Lazarus on 64-Bit Windows, and then rather to cross-compile your project to 64-Bit?

And many thx to the Lazarus-Devs
Title: Re: Lazarus Release 2.2.2
Post by: Martin_fr on May 19, 2022, 11:52:41 am
Quick question: Is it still the "official" recommendation, to use the 32-Bit Version of Lazarus on 64-Bit Windows, and then rather to cross-compile your project to 64-Bit?
Not sure where/when this recommendation came to be....

But I am using the 64 bit version.
[[EDIT: I am using fpc 3.2.3]]

And I would recommend, if you have a 64 bit PC and a 64bit Windows:
- If you compile all your projects to 32 bit, and 32 bit only: Use the 32bit IDE (just to save installing the cross compiler / the 64bit + cross32 will work just as fine)
- If you need the WinCe-arm - use the 32bit IDE.
- In all other cases use the 64bit IDE



>>EDIT:

Or maybe this was with regards to the 64bit fpc version 3.2.2

FPC 3.2.2 has several bugs that affect the generated code. Meaning the compiled project will end up with a bug.
They only occur in very rare situations.

One of this bugs has only been observed on Win64.
"observed" => i.e., it may well exist on other targets, it is just not known.
IIRC, in the meantime I heard about a 2nd such issue, that afaik was observed on Linux (not sure of the bitness).

At least the one bug that I observed was in the peephole optimizer.
Because the one place where it triggers is in the IDE (in FpDebug), if you want a working IDE, then you should compile Lazarus with -O1 if you rebuild it.

---
EDIT (3):
Just to clarify: A 32 bit IDE cross compiling to 64 bit, will badly impact the debugging abilities. Rather use a 64bit IDE compiled with -O1 (in case of rebuilding it / installing packages / just don't change the setting)
Title: Re: Lazarus Release 2.2.2
Post by: Zvoni on May 19, 2022, 01:58:19 pm
Thx for your answer, Martin.

I searched a bit, and the main issue (before Laz1.8 ) was SEH-handling, but that was before Laz1.8.
A second main issue was, that cross-compiling from Laz/FPC-64Bit to 32-Bit was buggy

At least those two are the main ones popping up researching the topic.

And yes, i know about the hassle about PtrInt, PtrUInt...
Title: Re: Lazarus Release 2.2.2
Post by: RayoGlauco on May 19, 2022, 03:02:24 pm
Many thanks to the lazarus developers!  :)
Title: Re: Lazarus Release 2.2.2
Post by: Martin_fr on May 19, 2022, 05:10:55 pm
I searched a bit, and the main issue (before Laz1.8 ) was SEH-handling, but that was before Laz1.8.
A second main issue was, that cross-compiling from Laz/FPC-64Bit to 32-Bit was buggy
SEH is now used by both 32 and 64 FPC for bit Windows.

I am not aware of issues with cross compiling.
There isn't an actual "cross compiler" because of the "Extended" type not existing in 64 bit.
So the "cross" compiler in the Lazarus distribution is actually a normal 32 bit compiler (I.e. the fpc/ppc.exe are 32 bit). So the result should really be the same as if you used the 32bit IDE, because the compiler is the same (it's renamed to fit in as a cross compiler...)

Cross debugging used to be an issue.
But it is no longer if you use the 64 bit IDE.
- The 64bit FpDebug can handle 64 and 32 bit projects.
- GDB can do both do, but needs a helper app (which is part of the setup)

The 32 bit IDE however can only cross debug a 64 bit target when using the gdb debugger.
Title: Re: Lazarus Release 2.2.2
Post by: bobby100 on May 19, 2022, 05:29:49 pm
Is it just me, or there is no way to install over the previous installation so that the configuration (installed components etc.) would be taken over?
I know it needs the IDE to get re-compiled, and that is not a problem to do, but I didn't found any other way to do it except to install every single component again.

I am still at 2.2.0 RC2 because of this - I just do not want to take the risk for my setup to get lost.

Any solution to my problem?
Title: Re: Lazarus Release 2.2.2
Post by: AFFRIZA 亜風実 on May 19, 2022, 06:23:11 pm
Thanks for the Lazarus developers!  O:-)

I'll update real quick.  ;)
Title: Re: Lazarus Release 2.2.2
Post by: Martin_fr on May 19, 2022, 08:28:05 pm
Is it just me, or there is no way to install over the previous installation so that the configuration (installed components etc.) would be taken over?
I know it needs the IDE to get re-compiled, and that is not a problem to do, but I didn't found any other way to do it except to install every single component again.
I am still at 2.2.0 RC2 because of this

Normally, there should be no need to reinstall anything.

1) If you choose to uninstall the prior version of Lazarus => The uninstaller has a checkbox, if it should delete configs. => Do not check it.

2) If you installed 3rd party packages, and they are not compatible, well yes, then you need to re-install / update yourself  (but if your current packages are RC compatible, they should be fine)

Quote
- I just do not want to take the risk for my setup to get lost.

Your setup is in the "primary config path" => Menu: View > Ide Internals > About IDE
Usually
Code: Text  [Select][+][-]
  1. C:\Users\<<YOUR_NAME>>\AppData\Local\lazarus
So, if you copy that directory, then you have all your settings copied.

There is one optional setup file in your install directory
Code: Text  [Select][+][-]
  1. C:\lazarus\lazarus.cfg
It exists in secondary installations, and has the path to the primary conf dir.

If you have downloaded packages in any other fold, and might need to update them, you can backup them too

OnlinePackageManager downloads are in the Primary Config dir.

If you open a project for testing, you might back it up too. Because the file format for lpi files changed. (Though 2.2 can save the old format too)


So with that you can always restore.
You can even copy your entire install dir. So you can copy it back, rather than doing a new install of the older version.


As for the windows registry. It has no IDE settings.
It only has info for innosetup. So Lazarus is in the list of installed apps, and you can uninstall it from there.
And it has file associations, so you can double click. But a new install leaves them intact.




Note if you put new versions of a 3rd party package in a new folder, the IDE still knows the old folder. It should update this once you open the package from the new location.

<primary conf path>\packagefiles.xml
Title: Re: Lazarus Release 2.2.2
Post by: korba812 on May 19, 2022, 09:31:13 pm
Quick question: Is it still the "official" recommendation, to use the 32-Bit Version of Lazarus on 64-Bit Windows, and then rather to cross-compile your project to 64-Bit?
IIRC The problem with cross compiling win64 to win32 is that the win64 platform does not know Extended (80bit float) type. Solution is software support for this type, but I don't know how much progress is being made on it, and probably only in trunk.
Title: Re: Lazarus Release 2.2.2
Post by: bobby100 on May 19, 2022, 09:44:38 pm
Thanks, Martin_fr, it worked. The only thing that was also needed is to re-compile the IDE at the end of the installation.
Title: Re: Lazarus Release 2.2.2
Post by: Martin_fr on May 19, 2022, 10:18:49 pm
Quick question: Is it still the "official" recommendation, to use the 32-Bit Version of Lazarus on 64-Bit Windows, and then rather to cross-compile your project to 64-Bit?
IIRC The problem with cross compiling win64 to win32 is that the win64 platform does not know Extended (80bit float) type. Solution is software support for this type, but I don't know how much progress is being made on it, and probably only in trunk.

AFAIK: The "extended" type is (one of?) the reason(s) why there is no official FPC cross compiler from Win64 to Win32.

However the "fpc cross compiler" for the official Lazarus does work. You can use a 64 bit IDE. Write an app that uses "Extended" and cross compile a 32 bit exe that will have proper "extended" values. The "fpc cross compiler" by Lazarus is a native 32bit FPC executable. The same FPC compiler that comes with the 32bit IDE, just renamed.

If you have a PC that can not run 32 bit executables then you have a problem. (Because then neither the 32bit IDE+fpc / nor the "cross fpc to 32bit" will work).

---
If you want to develop for 64 and 32 bit Windows => use the 64 bit IDE (restricted to -O1).
Title: Re: Lazarus Release 2.2.2
Post by: Rafael.Castro on May 20, 2022, 12:06:55 am
I Love Lazarus !  :)
Title: Re: Lazarus Release 2.2.2
Post by: Dimitrios Chr. Ioannidis on May 20, 2022, 10:21:04 am
Hi,

  can I ask which FPC branch/tag at gitlab this Lazarus release uses ?

  I tried to compile ppcrossavr for this particular FPC version from fixes_3_2 and from release_3_2_2 and I always get PPU invalid version .

Code: Pascal  [Select][+][-]
  1. [0.015] Unitsearch: system.ppu
  2. [0.015] Unitsearch: system.pp
  3. [0.015] Unitsearch: system.pas
  4. [0.015] Unitsearch: G:\Programming\dimitris\tools\laz-2.2.2_fpc-3.2.2\fpc\3.2.2\units\release\avr-embedded\avr5\rtl\system.ppu
  5. [0.015] PPU Loading G:\Programming\dimitris\tools\laz-2.2.2_fpc-3.2.2\fpc\3.2.2\units\release\avr-embedded\avr5\rtl\system.ppu
  6. [0.015] (SYSTEM)   PPU Name: G:\Programming\dimitris\tools\laz-2.2.2_fpc-3.2.2\fpc\3.2.2\units\release\avr-embedded\avr5\rtl\system.ppu
  7. [0.015] (SYSTEM)   PPU Invalid Version 208


EDIT: added Lazarus FPC output messages


regards,
Title: Re: Lazarus Release 2.2.2
Post by: jonyrh on May 20, 2022, 12:07:35 pm
Many thanks to all lazarus devs!  ::)
Title: Re: Lazarus Release 2.2.2
Post by: Martin_fr on May 20, 2022, 12:23:05 pm
  can I ask which FPC branch/tag at gitlab this Lazarus release uses ?

For Windows:

Tag release_3_2_2

SHA-1: 0d122c49534b480be9284c21bd60b53d99904346, Branch RevNo: 53220
*  * requiredversion to 3.2.0 and 3.2.2
Title: Re: Lazarus Release 2.2.2
Post by: Dimitrios Chr. Ioannidis on May 20, 2022, 12:57:18 pm
Hi,

  can I ask which FPC branch/tag at gitlab this Lazarus release uses ?

For Windows:

Tag release_3_2_2

SHA-1: 0d122c49534b480be9284c21bd60b53d99904346, Branch RevNo: 53220
*  * requiredversion to 3.2.0 and 3.2.2

thank you Martin .

regards,
Title: Re: Lazarus Release 2.2.2
Post by: Martin_fr on May 20, 2022, 01:14:16 pm
I just double checked. In my test install (created by the official installer), I went into the fpc ....../units/rtl dir and did
Code: Text  [Select][+][-]
  1. ppudump.exe fgl.ppu
and it outputs
Code: Text  [Select][+][-]
  1. Analyzing fgl.ppu (v207)

208 appears to be for 3.3.1.



use fpc -va
to see the exact files that fpc tries to load and use....
Title: Re: Lazarus Release 2.2.2
Post by: dseligo on May 20, 2022, 01:18:41 pm
Installed.
Kudos to developers.
Title: Re: Lazarus Release 2.2.2
Post by: Red_prig on May 20, 2022, 01:37:47 pm
Eh support for specific calling conventions
Code: Pascal  [Select][+][-]
  1. ms_abi_default
  2. ms_abi_cdecl
  3. sysv_abi_default
  4. sysv_abi_cdecl
  hasn't made it to release yet.
Title: Re: Lazarus Release 2.2.2
Post by: Martin_fr on May 20, 2022, 02:30:29 pm
Eh support for specific calling conventions
  hasn't made it to release yet.
Those sound like FPC features?

Then they will make it, when fpc does a release containing them.
I don't know if that will be 3.2.4 or 3.4.
Nor do I know when either of them will be released.
(You can but that query in the fpc section of the forum, or better (probably better likelihood to be seen by more fpc devs) on the fpc mail list.)

If/When either of them is released, Lazarus is likely to make a release soon after.
Title: Re: Lazarus Release 2.2.2
Post by: Red_prig on May 20, 2022, 02:38:40 pm
Eh support for specific calling conventions
  hasn't made it to release yet.
Those sound like FPC features?

Then they will make it, when fpc does a release containing them.
I don't know if that will be 3.2.4 or 3.4.
Nor do I know when either of them will be released.
(You can but that query in the fpc section of the forum, or better (probably better likelihood to be seen by more fpc devs) on the fpc mail list.)

If/When either of them is released, Lazarus is likely to make a release soon after.

These directives have been in the stable fpc branch for a long time (I can’t say from which version), but they are not supported by the lazarus text editor. Parsing errors will cause irritation. I wrote a patch for this case, but it's still in the main branch.
Title: Re: Lazarus Release 2.2.2
Post by: piola on May 20, 2022, 02:51:17 pm
Cross debugging used to be an issue.
But it is no longer if you use the 64 bit IDE.
- The 64bit FpDebug can handle 64 and 32 bit projects.
- GDB can do both do, but needs a helper app (which is part of the setup)

Does this also mean, that cross-compiling from Lazarus/FPC x64 to Linux x64 is possible now? I used to get "internal error 200208151" in this case.
Title: Re: Lazarus Release 2.2.2
Post by: piola on May 20, 2022, 02:54:45 pm
Thank you very much for the new release! With 2.2.0 I was a little afraid that Lazarus development could be ceased, but I'm happy to see that development is continuing! 👍
Title: Re: Lazarus Release 2.2.2
Post by: Martin_fr on May 20, 2022, 03:14:06 pm
These directives have been in the stable fpc branch for a long time (I can’t say from which version), but they are not supported by the lazarus text editor. Parsing errors will cause irritation. I wrote a patch for this case, but it's still in the main branch.
Ok, I see.

The person who applied your patch, has to decide if he deems it "merge-able".

Usually this decision starts with: Is it a bug-fix (then maybe yes, if otherwise safe) or is it a feature (then 99.9% no).

From the description I would deem it a bug-fix.
Title: Re: Lazarus Release 2.2.2
Post by: Martin_fr on May 20, 2022, 03:26:54 pm
Does this also mean, that cross-compiling from Lazarus/FPC x64 to Linux x64 is possible now? I used to get "internal error 200208151" in this case.
I haven't tested that, so I don't know.
There is no cross compiler supplied by us.

But from what I hear, if you have a cross compiler for that target, you will need certain library files for it to work.


If FPC gives you a "internal error ...." then this normally always is a bug in FPC that should be reported (at least if it can be reproduced).

However, does the FPC team has an officially released cross compiler for this? (I haven't checked)
And is that the one you use?

If not, you may check on the mail list.

Though, if
- you build it yourself
- you can supply git-SHA and exact commands you used to build it
- you have steps to reproduce the error
then I would think it should be reported.

Because, if you do something that is not supported => you should get a proper error, but not an "internal error".


Title: Re: Lazarus Release 2.2.2
Post by: Martin_fr on May 20, 2022, 03:31:52 pm
With 2.2.0 I was a little afraid that Lazarus development could be ceased, but I'm happy to see that development is continuing! 👍
Just monitor https://gitlab.com/freepascal.org/lazarus/lazarus/-/commits/main and you will see the progress.

For the fixes branch:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/commits/fixes_2_2
https://gitlab.com/freepascal.org/lazarus/lazarus/-/network/fixes_2_2?extended_sha1=&filter_ref=1

Title: Re: Lazarus Release 2.2.2
Post by: marcov on May 20, 2022, 03:32:23 pm
Does this also mean, that cross-compiling from Lazarus/FPC x64 to Linux x64 is possible now? I used to get "internal error 200208151" in this case.

Probably not. You can't crosscompile from a target that doesn't have 80-bit extended to one that does. Or at least that is currently not supported.

Note that codetyphon packages FPC versions that are not stable releases.
Title: Re: Lazarus Release 2.2.2
Post by: piola on May 20, 2022, 08:13:23 pm
Does this also mean, that cross-compiling from Lazarus/FPC x64 to Linux x64 is possible now? I used to get "internal error 200208151" in this case.

Probably not. You can't crosscompile from a target that doesn't have 80-bit extended to one that does. Or at least that is currently not supported.

Note that codetyphon packages FPC versions that are not stable releases.

Yes, that's the exactly the point which I do not understand: From Win64 to Linux64 -> same architecture, so both do not have Extended. But it doesn't work anyway  ::)
Title: Re: Lazarus Release 2.2.2
Post by: tetrastes on May 20, 2022, 09:41:51 pm
Yes, that's the exactly the point which I do not understand: From Win64 to Linux64 -> same architecture, so both do not have Extended. But it doesn't work anyway  ::)

Linux 64 bit has Extended, quote from https://www.freepascal.org/docs-html/current/ref/refsu5.html#x27-310003.1.2:
Quote
the extended type is available on all Intel x86 processors, except on the Windows 64-bit platform
Title: Re: Lazarus Release 2.2.2
Post by: piola on May 20, 2022, 10:23:39 pm
Okay...  I do understand even less now %)

I thought it was a the AMD64 architecture to lack support for 80bit-floats, but it's obviously the Win64 libraries which do not provide 80bit-float API functions. Is this the correct interpretation?

So if I go back to using 32bit-Lazarus, I should be able to cross-compile both for Win64 and Linux64, right?
Title: Re: Lazarus Release 2.2.2
Post by: dbannon on May 21, 2022, 01:52:19 am
So if I go back to using 32bit-Lazarus, I should be able to cross-compile both for Win64 and Linux64, right?

One approach that might be easier. Use VirtualBox on your windows machine, make a Linux VM for it and call that your "release VM", from there you can pretty easily compile Linux32/64 and Windows32/64 (and Raspberry Pi etc ).  Having that VM there set aside for the final build and test is good too.

My build and package script https://github.com/tomboy-notes/tomboy-ng/blob/master/package/package.bash needs a fair bit of infrastructure around it and it does require the final Inno Setup stage done on Windows but it does make the release very easy. To setup the cross compilers see https://wiki.freepascal.org/Cross_compiling .

I suggest if you need more help, probably should open a new forum thread, its not really an Lazarus issue (its a FPC one)and certainly not Lazarus 2.2.2. one.

Davo

Title: Re: Lazarus Release 2.2.2
Post by: PeaZomboss on May 21, 2022, 10:42:07 am
In fact you can use FPU through assembler by hand to use Extended float on Windows x64,
but I don't know why MS don't like FPU while Linux x64 use it. ;)
Title: Re: Lazarus Release 2.2.2
Post by: Espectr0 on May 21, 2022, 04:04:15 pm
Many thanks to the lazarus developers!!
Title: Re: Lazarus Release 2.2.2
Post by: cpalx on May 22, 2022, 03:34:39 am
Thanks all Devrlopers
Title: Re: Lazarus Release 2.2.2
Post by: 440bx on May 22, 2022, 04:24:26 am
Another thank you and expression of appreciation for all the hard work the team consistently puts into making Lazarus ever better.
Title: Re: Lazarus Release 2.2.2
Post by: BrunoK on May 22, 2022, 03:55:21 pm
Win 10, Display text size = 200% (Laptop high resolution)
Project -> Options -> Custom Options -> All Options
 displays like in the attachment.

in ide\allcompileroptions.pas at lines near 350, adding   
Container.Perform(CM_PARENTFONTCHANGED, 0, 0) corrects the line spacing.

Code: Pascal  [Select][+][-]
  1.   Container := sbAllOptions;
  2.   Container.Perform(CM_PARENTFONTCHANGED, 0, 0); // ~bk
  3.   Container.DisableAutoSizing{$IFDEF DebugDisableAutoSizing}('TfrmAllCompilerOptions.RenderAndFilterOptions'){$ENDIF};

Title: Re: Lazarus Release 2.2.2
Post by: folkeu08 on May 22, 2022, 07:01:24 pm
Hi,
I'm using lazarus in portable mode on a USB key.
Before installation, I create in the directory dedicated to lazarus a file named "lazarus.cfg" containing these values ​​"--primary-config-path=e:\lazarus_2.2.2\lazconfig".
When I add the installation package "sqlite3laz", and the application recompiles, I get an error message when I launch it (see the attachment). Is this normal?
With version 2.2.0, I didn't have it.
Thank you

Title: Re: Lazarus Release 2.2.2
Post by: Martin_fr on May 22, 2022, 08:36:28 pm
Hi,
I'm using lazarus in portable mode on a USB key.
Before installation, I create in the directory dedicated to lazarus a file named "lazarus.cfg" containing these values ​​"--primary-config-path=e:\lazarus_2.2.2\lazconfig".
When I add the installation package "sqlite3laz", and the application recompiles, I get an error message when I launch it (see the attachment). Is this normal?
With version 2.2.0, I didn't have it.
Thank you

From Microsoft's page
Code: Text  [Select][+][-]
  1. Error 0x7b
  2. The filename, directory name, or volume label syntax is incorrect.

Do you have the sqlite dll installed (matching 64/32 bit depending on what Lazarus bit-ness you have?
Title: Re: Lazarus Release 2.2.2
Post by: folkeu08 on May 22, 2022, 09:31:08 pm
Hi Martin_fr,
You have right. It's a new install and the dll is not present
I add a line in my tuto to install on a usb Stick.
Very thanks.
François
Title: Re: Lazarus Release 2.2.2
Post by: JuhaManninen on May 23, 2022, 10:04:05 am
Win 10, Display text size = 200% (Laptop high resolution)
Project -> Options -> Custom Options -> All Options
 displays like in the attachment.

in ide\allcompileroptions.pas at lines near 350, adding   
Container.Perform(CM_PARENTFONTCHANGED, 0, 0) corrects the line spacing.

Code: Pascal  [Select][+][-]
  1.   Container := sbAllOptions;
  2.   Container.Perform(CM_PARENTFONTCHANGED, 0, 0); // ~bk
  3.   Container.DisableAutoSizing{$IFDEF DebugDisableAutoSizing}('TfrmAllCompilerOptions.RenderAndFilterOptions'){$ENDIF};
Luckily I noticed this and added the line in 59eeb39742. Will be merged to fixes branch.
Title: Re: Lazarus Release 2.2.2
Post by: Al-Eid on May 24, 2022, 12:57:06 pm
thank you all  :)
Title: Re: Lazarus Release 2.2.2
Post by: Milsa on May 27, 2022, 04:24:37 pm
Configuration path error for fppkg is still not fixed.

My Lazarus path is (for secondary installation):
D:\Windows\Programy\lazarus\

Config path is (for secondary installation):
D:\Windows\Programy\lazarus\config\

Fppkg still save configuration file to local file:
C:\Users\---\AppData\Local\FreePascal\fppkg\fppkg.cfg

Correct configuration file must be:
D:\Windows\Programy\lazarus\config\fppkg.cfg

Please fix it, this is issue for it:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39612
Title: Re: Lazarus Release 2.2.2
Post by: 12398890 on May 29, 2022, 06:44:18 pm
Many thanks to the lazarus developers.
Title: Re: Lazarus Release 2.2.2
Post by: RadDeveloper on June 20, 2022, 06:38:34 am
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.
Title: Re: Lazarus Release 2.2.2
Post by: Handoko on June 20, 2022, 07:19:58 am
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
Title: Re: Lazarus Release 2.2.2
Post by: JuhaManninen on June 20, 2022, 08:48:31 am
It seems to be reported :
 https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39745
Title: Re: Lazarus Release 2.2.2
Post by: RadDeveloper on June 21, 2022, 07:36:47 am
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 :(
Title: Re: Lazarus Release 2.2.2
Post by: dseligo on June 21, 2022, 10:33:55 am
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)?
Title: Re: Lazarus Release 2.2.2
Post by: jipété on June 21, 2022, 11:08:10 am
I confirm what RadDeveloper said is reproducible on Lazarus 2.2.2 Linux GTK2.
Also in old 2.2.0.
Title: Re: Lazarus Release 2.2.2
Post by: RadDeveloper on June 21, 2022, 10:05:07 pm
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 :-)
Title: Re: Lazarus Release 2.2.2
Post by: dseligo on June 21, 2022, 10:16:05 pm
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).
Title: Re: Lazarus Release 2.2.2
Post by: Martin_fr on June 21, 2022, 10:29:21 pm
Or your app depends on some dll, that you did not put in the new install?

Quote
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.
Title: Re: Lazarus Release 2.2.2
Post by: RadDeveloper on June 21, 2022, 11:12:02 pm
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.
Title: Re: Lazarus Release 2.2.2
Post by: RadDeveloper on June 21, 2022, 11:16:53 pm
Or your app depends on some dll, that you did not put in the new install?

Quote
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.
Title: Re: Lazarus Release 2.2.2
Post by: RadDeveloper on June 21, 2022, 11:18:31 pm
I suspect that 64 bit debugger tried to debug 32 bit app.
TinyPortal © 2005-2018