Forum > Lazarus

We are planning the release of Lazarus 2.2

<< < (8/10) > >>

Martin_fr:

--- Quote from: ssawgift on June 23, 2021, 03:32:27 am ---
--- Quote from: Martin_fr on June 22, 2021, 06:36:42 pm ---gdb based or fpdebug?
EDIT:
Btw, how much mem is used on your system?

--- End quote ---
I don't know. I am just a casual user of Lazarus. I use F9 to debug.

--- End quote ---

Well the mem usage is in the task manager: run taskmgr.exe

The debugger type: Tools > Options > Debugger > debugger backend
Look in the top tool-bar, it should either have something with fpdebug, or with gdb (or gnu)

The reason I asked is, that the default changed, and it depends on if you had an earlier install, and that the new default actually worked.

You can also (in the top toolbar) toggle between the two, and see if one is better that the other.

ssawgift:

--- Quote from: Martin_fr on June 23, 2021, 10:45:36 am ---
--- Quote from: ssawgift on June 23, 2021, 03:32:27 am ---
--- Quote from: Martin_fr on June 22, 2021, 06:36:42 pm ---gdb based or fpdebug?
EDIT:
Btw, how much mem is used on your system?

--- End quote ---
I don't know. I am just a casual user of Lazarus. I use F9 to debug.

--- End quote ---

Well the mem usage is in the task manager: run taskmgr.exe

The debugger type: Tools > Options > Debugger > debugger backend
Look in the top tool-bar, it should either have something with fpdebug, or with gdb (or gnu)

The reason I asked is, that the default changed, and it depends on if you had an earlier install, and that the new default actually worked.

You can also (in the top toolbar) toggle between the two, and see if one is better that the other.

--- End quote ---
Memory is not a problem at all. Official 2.0.12 release works perfectly on W2k.

I have only one debugger (gdb) so that means 2.2RC may have a problem with gdb debugging (with -g flag).

I also tried fpdebug and found that it does not step into components source code as gdb. For example, pressing F7 on self.Caption := 'any' does not automatically go to control.inc.

Martin_fr:

--- Quote from: ssawgift on June 23, 2021, 02:59:44 pm ---Memory is not a problem at all. Official 2.0.12 release works perfectly on W2k.

I have only one debugger (gdb) so that means 2.2RC may have a problem with gdb debugging (with -g flag).

I also tried fpdebug and found that it does not step into components source code as gdb. For example, pressing F7 on self.Caption := 'any' does not automatically go to control.inc.

--- End quote ---

** Gdb: There a quite a few things that may be....

- As you build trunk yourself, you did not download a new gdb version => so you use the same version as before (no change here).

- There have been changes on the IDE site. Dealing with SEH exceptions, and other stuff. I don't know how much of an impact they have.

- Compare the filesize of the project.exe that you are debugging => if it has changed massively between 2.0.12 and trunk, then maybe some packages had debug info added, that did not have it before. But that would only make a diff, if memory was low..

- 2.2 Will come with a diff gdb version.
https://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2064%20bits/Alternative%20GDB/GDB%209.2%20-%20Modified%20for%20unicode/
https://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2032%20bits/Alternative%20GDB/GDB%209.2%20%28cygwin%29/

I do not know, if that will be good for older windows, but you can download different gdbs from our sourceforge page.

** FpDebug
You are using 32 bits?
Then -g may still mean "stabs" (see entries under "debug info type" in project options.

Fpdebug only supports dwarf (you will have noted the pop up).
That pop up only changed your project.
It did not affect the packages.

If you build packages with -gw then that will work.
=> Most packages use the "IDE build options" => go to Tools > Configure build lazarus => and add the option there (Press "Save" to exit, no need to build)

There are different dwarf versions.
- If you plan to also use gdb or go back to gdb => stick to version 2 (or later change it back). gdb has some extra crashes with dwarf version 3
  In that case use the options
  -gw -godwarfsets

- If you decide to stick with fpdebug (or change options as you change debugger)
  Use
  -gw3

dwarf 3 gives you upper/lowercase names => nice.

You can mix dwarf 2 and 3. Eg compile packages with dwarf 2, and the project with dwarf 3 (for fpdebug)

If FpDebug works for you => I do recommend it.

dbannon:
... getting back to the release candidate.

On the Mac, fixes_2_2 builds, by default a 64bit IDE etc.  Good.  But when you first start Lazarus, without an existing configuration, it first finds and suggests the ppc386 compiler. And says its OK.  I don't think so.

Secondly, the same initial config assumes we are going to use gdb, I thought lldb was the preferred debugger on MacOS ?

In my case the scanning for FPC source seemed to not work too. I waited ten minutes before I stopped and entered the location manually. It appeared to be starting in the right place, /usr/local/share/fpcsrc and that dir on my system contained only an old install of 3.0.4 and the 3.2.0 so not a lot of searching needed. but my Mac is pretty old ...

Davo

ASerge:

--- Quote from: Gald on June 22, 2021, 09:38:22 am ---Even Embarcadero already dropped support for Win7 few years ago.

--- End quote ---
This is incorrect.
Applications of the latest version of Delphi can, according to the documentation, run on Windows 10, Windows 8.1, Windows 7 (SP1+), Windows Server 2019, Windows Server 2016, and Windows Server 2012 R2.
Moreover, the IDE itself also works on the same platforms.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version