Lazarus

Using the Lazarus IDE => General => Topic started by: Gald on September 28, 2021, 06:47:26 am

Title: [Solved] New Proj with no code: "the debugger encountered an error msg="Warning"
Post by: Gald on September 28, 2021, 06:47:26 am

This project is all empty, it was just a test of colors, but I can't run it anymore.
The only thing a did before run it again was to change a panel's color.
Some file is corrupted, maybe?

Title: Re: New Proj with no code: "the debugger encountered an error msg="Warning\nCannno"
Post by: trev on September 28, 2021, 07:00:35 am

What versions of Windows, FPC and the Lazarus IDE are you sing?

Did you set the breakpoint which is causing the issue?

Title: Re: New Proj with no code: "the debugger encountered an error msg="Warning\nCannno"
Post by: Gald on September 28, 2021, 07:53:19 am

Windows 10 (64) and Lazarus 2.0.12.
There is no breakpoint and I did nothing on the source editor.
It's everything on the screenshot.
Also, the program project is ok with no modifications.

Title: Re: New Proj with no code: "the debugger encountered an error msg="Warning\nCannno"
Post by: trev on September 28, 2021, 08:40:55 am

The error suggests that a breakpoint has been set, possibly on line 43 of unit1.pas.

What happens if you choose the run the program without debugging? Lazarus > Run > Run Without debugging?

Title: Re: New Proj with no code: "the debugger encountered an error msg="Warning\nCannno"
Post by: Martin_fr on September 28, 2021, 11:10:31 am

43 is not the line number.

But otherwise, yes what Trev said.
Go to the "breakpoint window" and see what breakpoints you have. One of them can not be set.

This can for example happen when a breakpoint was set "by address" (eg in the asm window), and that address is no longer in the exe.

Title: Re: New Proj with no code: "the debugger encountered an error msg="Warning\nCannno"
Post by: Gald on September 28, 2021, 03:40:54 pm

Well done!

I did nothing, I swear!
Have no idea how this breakpoint is there, but by removing it, the app is running again.
Thank you both, Trev and Martin!
 :D