Lazarus Release Candidate 2 of 3.0

[mattias]

The Lazarus team is glad to announce the second release candidate of Lazarus 3.0.

This release was built with FPC 3.2.2.

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

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

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

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

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

Minimum requirements:

Windows:
  2k, 32 or 64bit, Qt, Qt5, Qt6 (64bit only)

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

Mac OS X:
  Cocoa (64bit) 10.12, Carbon (32bit) 10.5 to 10.14, Qt and Qt5 (32 or 64bit), Qt6 (64bit only).

There is a problem on Macos. When upgrading from Ventura to Sonoma 13.6, debugging in the IDE often does not work, the app does not start. Running the app without debugging and debugging in the Terminal using lldb does work.
Once a solution is found I will upload a new Lazarus pkg for Macos.

[jonyrh]

Thx! 

[d7_2_laz]

Great!
Recompiled my major apps, Win10 x64. Nearly(*) flawlessly  ... as in RC1, no more patching needed (completely different to 2.2.x).
Thousand thanks for this excellent development tool and the contributors involved!

(*) The only thing i saw at one of my apps:
When doing "Start" (green arrow icon), after compile & link, there is no error message, but the project's executable won't start.
- When i now start the executable from outside the IDE (via double click in win explorer), i will be thrown within the IDE again
- When having closed the IDE and start the generated exe, it will start regularly and correctly
Compile mode is "Default". Install is a secondary install. Config dir is within the RC2 folder.
Where does this might point to? Never saw such.

Retried with RC1: behaves as expected.

[Bart]

(*) The only thing i saw at one of my apps:
When doing "Start" (green arrow icon), after compile & link, there is no error message, but the project's executable won't start.
- When i now start the executable from outside the IDE (via double click in win explorer), i will be thrown within the IDE again
- When having closed the IDE and start the generated exe, it will start regularly and correctly
Compile mode is "Default". Install is a secondary install. Config dir is within the RC2 folder.
Where does this might point to? Never saw such.

Please report on the bugtracker.
It would be great if you can bisect the guilty revision...

Bart

[Martin_fr]

(*) The only thing i saw at one of my apps:
When doing "Start" (green arrow icon), after compile & link, there is no error message, but the project's executable won't start.
- When i now start the executable from outside the IDE (via double click in win explorer), i will be thrown within the IDE again
- When having closed the IDE and start the generated exe, it will start regularly and correctly
Compile mode is "Default". Install is a secondary install. Config dir is within the RC2 folder.
Where does this might point to? Never saw such.

1) Which debugger do you use? Tools > debugger > debugger backend.
FpDebug or GDB?

2)
lazarus --debug-log=somelogfile.txt

And once the issue has happened, submit the logfile.

3) Any antivirus software?
Maybe (for testing) exclude the project dir (where the exe is) from Windefender.

[d7_2_laz]

Please report on the bugtracker.

I would have done so if i only were able to provide a simplified test case, but i can't.
The only i have is the behaviour, and, if needed, the compile/link event log, but there's nothing suspicious herein. So my hope was that somebody may have an idea about a possible source resp. an indication how to track it down.

Addendum when the app has been compiled/linked, and i press "Start" again, nothing won't happen and the message window is empty.
But the executable is correctly generated and startable from outside if the IDE is closed.

Lazarus 3.0RC2 (rev lazarus_3_0_RC2) FPC 3.2.2 x86_64-win64-win32/win64

Debugger

is FPDebug.

Antivirus / Windows Defender

:  The output folder now is excluded from Win Defender  -> no difference

Logfile

Is attached

[d7_2_laz]

Debugger

The same happens when having set (within Tools > debugger) the debugger backend to GDB.

[Martin_fr]

Is it just the one project?

Other old projects work or not?
New empty form ?

[Martin_fr]

Have you tried: Run > Reset Debugger ?

Though if you just started the IDE, then there would be nothing to be reset...

[Martin_fr]

Any Pas2Js packages installed?


Could you recompile the IDE with
-dVerboseDebugger -dDBG_VERBOSE -dDBG_WARNINGS
and provide another log?

[d7_2_laz]

Is it just the one project?
Other old projects work or not?

Yes, three others (basically having a near similar structure)  behave fine
And so,  a new empty form project behaves fine too.

Reset debugger / just started the IDE

The IDE just had been started anew

Any Pas2Js packages installed?

No,  and else nothing special differently to other apps  here: laz,virtualtreeview_package, DateTimeCtrls, LazUtils, LCL

Recompile the IDE with ...

Sorry Martin, as i'm not so familiar here, what would be the full syntax for that when usinig the command prompt (or, or howto from inside the IDE)?

[Martin_fr]

To rebuild the IDE: Tools menu > Configure build IDE

Drop the arguments into the "custom options" memo. Then build, and restart.

If you don't mind, could you send the lpi and lps file (can be sent in private, via pm or lazarus <symbol> mfriebe.de

Mind the lps may be part of the lpi. Or it could be saved in the primary config path, under project sessions.
Find the PCP: Menu View > Ide Internals > About IDE

[Jonax]

  Thanks again to the Lazarus team for your efforts and hard work. Previous RC works fine for my modest needs. Will try the new one later.

[michaelthuma]

Is it just the one project?

Other old projects work or not?
New empty form ?

I just installed the new RC and started a project from scratch. A special behavior unfolded.

Once the dialog box asking you to enable DWARF3 or don't debug showed up the behavior is not different to the past. - That's my personell conclusion from what I observed and can no longer reproduce.

a) First new project

The project started/application built from scratch started to run without debugging. After creating both build modes Debug and Release in Project Options the dialog box mentioned before showed up and everything started to work smoothly.

b) Second new project
The next new project started does not suffer from this special behavior, which seems to be gone imho. Build modes were not enabled in the project options.

Lazarus 3.0 RC2 Win32 and cross compilation installed at least.

I didn't pay much attention because that happend in the past too.

In general RC2 works good for me. Congratulations!

[Martin_fr]

Once the dialog box asking you to enable DWARF3 or don't debug showed up the behavior is not different to the past. - That's my personell conclusion from what I observed and can no longer reproduce.

I am not exactly sure if I follow...

If you have a new project the dialogs shows once for that project.
Then the choice is saved, and that project will not ask again (well, if you had chosen one of the Dwarf settings.


If you do build modes, the dialog shows once  when you run the first time for debug.
The dialog does not show in the "release" build mode.
=> This is only if the project was created with Lazarus 3.0. Projects that have a release build mode from earlier Lazarus versions will ask in release mode too (which makes no sense).
=> In Lazarus 3.0: Release mode means to run without debugger by default.

If you have at any time opened the project-options, and debug info was set to "dwarf...", and you checked "Set compiler options as default" (lower left corner), and pressed "ok" => then dwarf is default for all new projects, and the dialog will not happen for new projects.