Best Way To Fix The Error, The Debugger Entered An Error State

Approved: Fortect

1. Download Fortect and install it on your computer

2. Launch the program and click "Scan"

3. Click "Repair" to fix any issues that are found

Speed up your computer's performance now with this simple download.

You should read these repair ideas if the debugger has entered an error status error code on your computer.

When I run a program in Lazarus from F7 (input) or F8 (input), it compiles, this program runs, but after a moment it looks like an error:
“Debugger error

< p> Sorry, the debugger has entered an error state.
Save your work! “
While F9 runs fine.
What can I do?

“Last modified: December 7, 2011 12:15:18 PM by-Panoss”

Connected

Windows 7 32-bit, Lazarus v1.8.4 FPC 3.0.4.

There are many possible reasons:

If this happens when launching the application: find the forum for working with Bitdefender and the comodo Firewall.

Under Very Difficult Cases, turn on the printer or change the default to another printer. Heard a few random / unconfirmed answers, some printer drivers are causing GDB to crash a little (Lazarus uses GDB)

Approved: Fortect

Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.

1. Download Fortect and install it on your computer

2. Launch the program and click "Scan"

3. Click "Repair" to fix any issues that are found

Definitely:

Updatepre-Lazarus 0.9.30.2

Follow the download link on this forum, you will find it at Sourceforge.

Many bugs have been fixed and a GDB (win) update is also coming out.
Later checked that So, update the config referenced by the idea to update GDB. (On Linux make sure you have GBB 7.2 or large / on Mac definitely 6.3.50)
See http://wiki.lazarus.freepascal.org/Debugger_Setup

For more help, please get the important information described here:
http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#Create_a_new_Report.

( You can skip recompiling with any of our definitions)

Connected

AuthorSubject: Debugger Error Sorry, The Debugger Has Introduced An Error (4110 Reads)

If I run media in Lazarus from F7 (input) or F8 (input), it compiles, the program runs, although an error is displayed instantly:
“Debugger error

Sorry, all debuggers have reached an error state
Save your work now with! “
with normal F9 expansion.
What can I dob?

“Last modified: December 2, 2011 12:15:18 PM by Panoss”

If you walk by your house when launching the store app: this forum is for bitdefender related to comodo firewall.

In very rare cases, turn on this printer or change the default to find another printer. I’ve heard occasional / unconfirmed reports that some printer drivers are causing GDB to crash in some way (Lazarus uses GDB)

Follow the download link in this forum, you should find Sourceforge.

Many glitches have been fixed and an updated GDB (Win) has been added.
So, after the update, check the config type pointing to the updated GDB. (On Linux, make sure you have GBB 7.2 or higher / Apple PC only has 6.3.50 available)
See http://wiki.lazarus.freepascal.org/Debugger_Setup

Some time ago I installed Lazarus (version 1.4.4) on a mini Mac (OSX 10.10 Yosemite) including the GDB debugger. When I compile and run a perfect simple application – like an empty form – everything you know is fine. Unfortunately, when I close the running applicationi get a message

GDB generates an internal error: click OK to continue. debug. It might NOT be sure. Click Stop to complete troubleshooting. Session.

Unfortunately, the installed debugger has an error status. Get yourself a job now. Cut Stop and hope for the best; remove the plug.

I choose “stop” on a strange message and everything is fine. Should we expect this? The “Show message on shutdown” and “Reset debugger after every startup” options are not selected in the custom debugger. … I saw this information about a similar error, it is several years old and is no longer relevant.

Speed up your computer's performance now with this simple download.