Forum > Lazarus

Lazarus Release Candidate 1 of 2.2.0

<< < (3/27) > >>

c600g:
I installed RC1 on my Linux box (KDE Neon, so I used the 64-bit deb files), following these steps:

1. Saved my old .lazarus/ directory to start fresh with the new RC
2. Installed the following packages: anchor docking design, sparta docked form editor, weblaz.
3. Edited Lazarus options for preferred font config, colors, tabs, etc.
4. Installed Lazarus Docked Desktops Studio Plus Complete desktop configuration XML file.

Then, I opened an existing application project to see how well FpDebug worked (the new default debugging back end).

Issue #1

Unfortunately, when Lazarus switched to the default debug desktop upon hitting a breakpoint, Lazarus appeared to be unresponsive. If I hit 'F9' to continue the application, the application would run, but I could not interact with the Lazarus window at all. When I shut down the application, Lazarus was still unresponsive. I could close it down using the WM controls, but that was it.

Doing a bit of experimentation, it seems as if switching to the "debug docked" desktop configuration is causing the issue. If I set the "default docked" desktop as the debug desktop, debugging is possible.

Issue #2

Using the FbDebug back end, the local variables window does not look correct (see attachment).

Issue #3

One of my existing projects is a shared library. It does not appear that I can debug shared libraries using FpDebug, which is consistent with what I see here.

Looks as if I will have to continue to use GDB to debug libraries.

Hope this helps!
  Alan

Martin_fr:

--- Quote from: c600g on July 12, 2021, 07:53:58 pm ---Issue #1

Unfortunately, when Lazarus switched to the default debug desktop upon hitting a breakpoint, Lazarus appeared to be unresponsive. If I hit 'F9' to continue the application, the application would run, but I could not interact with the Lazarus window at all. When I shut down the application, Lazarus was still unresponsive. I could close it down using the WM controls, but that was it.

Doing a bit of experimentation, it seems as if switching to the "debug docked" desktop configuration is causing the issue. If I set the "default docked" desktop as the debug desktop, debugging is possible.

--- End quote ---
Could you please check, if switching between fpdebug and gdb-debug has an effect an this?



--- Quote ---Issue #2

Using the FbDebug back end, the local variables window does not look correct (see attachment).

--- End quote ---
Ah, yes. On Linux (at least gtk) the component (not sure which one does the display) does multiline.
FpDebug delivers multiline.
Still, the empty lines are not explained (and the multiline may not be desirable).

Please report. (report in category debugger, so it goes straight to me).
I am busy / partly unavailable in the upcoming days / rest of the month.  But I will see if I can get to this.



--- Quote ---One of my existing projects is a shared library. It does not appear that I can debug shared libraries using FpDebug, which is consistent with what I see here.

--- End quote ---

Indeed, but you can switch debugger on a per project base.
It's in the project options (first half).

Though if you use the project between several IDE (eg different PC) then that fails. As the setting stores on OID, that is specific to each IDE (you can of course copy this in the environment opts)

c600g:

--- Quote from: c600g on July 12, 2021, 07:53:58 pm ---Issue #1

Unfortunately, when Lazarus switched to the default debug desktop upon hitting a breakpoint, Lazarus appeared to be unresponsive. If I hit 'F9' to continue the application, the application would run, but I could not interact with the Lazarus window at all. When I shut down the application, Lazarus was still unresponsive. I could close it down using the WM controls, but that was it.

Doing a bit of experimentation, it seems as if switching to the "debug docked" desktop configuration is causing the issue. If I set the "default docked" desktop as the debug desktop, debugging is possible.

--- End quote ---


--- Quote from: Martin_fr on July 12, 2021, 08:09:18 pm ---Could you please check, if switching between fpdebug and gdb-debug has an effect on this?

--- End quote ---

I just tried switching the debugger to gdb in the Project Options, set the debug desktop as "debug docked", and it worked fine. Then I switched it back to IDE-Default (which is FbDebug) and now it works fine as well... ? I'm not sure what I did to resolve the issue, but it appears to be working at the moment.


--- Quote from: c600g on July 12, 2021, 07:53:58 pm ---Issue #2

Using the FbDebug back end, the local variables window does not look correct (see attachment).

--- End quote ---


--- Quote from: Martin_fr on July 12, 2021, 08:09:18 pm ---Ah, yes. On Linux (at least gtk) the component (not sure which one does the display) does multiline.
FpDebug delivers multiline.
Still, the empty lines are not explained (and the multiline may not be desirable).

Please report. (report in category debugger, so it goes straight to me).
I am busy / partly unavailable in the upcoming days / rest of the month.  But I will see if I can get to this.

--- End quote ---

Will do.


--- Quote from: c600g on July 12, 2021, 07:53:58 pm ---One of my existing projects is a shared library. It does not appear that I can debug shared libraries using FpDebug, which is consistent with what I see here.

--- End quote ---


--- Quote from: Martin_fr on July 12, 2021, 08:09:18 pm ---Indeed, but you can switch debugger on a per project base.
It's in the project options (first half).

Though if you use the project between several IDE (eg different PC) then that fails. As the setting stores on OID, that is specific to each IDE (you can of course copy this in the environment opts)

--- End quote ---

Yes, I noticed that it stores an OID, and will have to set it for each different PC I work on and ignore the difference before committing, I guess.

Thanks again,
  Alan

Martin_fr:

--- Quote from: c600g on July 12, 2021, 08:29:57 pm ---I just tried switching the debugger to gdb in the Project Options, set the debug desktop as "debug docked", and it worked fine. Then I switched it back to IDE-Default (which is FbDebug) and now it works fine as well... ? I'm not sure what I did to resolve the issue, but it appears to be working at the moment.

--- End quote ---

There are plenty reports from people that using any debugger, have occasionally the desktop freezing on Linux. Especially with breakpoint in certain events (OnMove).

But I understand your desktop (Linux) was fine. Only Lazarus was not.

If you run the IDE from a console/terminal you may catch output from the IDE, if there is a crash or anything.

c600g:

--- Quote from: Martin_fr on July 12, 2021, 08:38:04 pm ---There are plenty reports from people that using any debugger, have occasionally the desktop freezing on Linux. Especially with breakpoint in certain events (OnMove).

But I understand your desktop (Linux) was fine. Only Lazarus was not.

--- End quote ---

Correct. It was as if Lazarus was not able to switch to the debug desktop and the visible UI froze, although pressing F9 did cause the application being debugged to resume.
 

--- Quote from: Martin_fr on July 12, 2021, 08:38:04 pm ---If you run the IDE from a console/terminal you may catch output from the IDE, if there is a crash or anything.

--- End quote ---

If I can reproduce the issue again, I will do that. I've submitted an issue for the FpDebug / Local Variables on Mantis as well.

Cheers,
  Alan

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version