FPC(2.4.2 and 2.4.4) crash after closing lazarus / 12-Debugger ---------------------------------------------------------------------- christensen · 2011-08-07 09:46 When i close the running program the FPC is crashing and Lazarus remaining in debug mode. when is happening  that and i try to run again all is fine till the program execution(linking the exe) which will not going to happen, only some times and after that the fpc crash is coming.I've change the FPC versions from FPC 2.4.2 to 2.4.4 but the same.The compiler is compiling the project/program i can execute it from windows explorer. My system: Lazarus V0.9.30 (FPC 2.4.2 and 2.4.4) on Windows 7 Ultimate 32-bit (AMD Athlon 7750 black edition Asus M3N78-CM). On the same PC but with Windows XP SP3 32-bit is running wonderful. error: QuoteProblem signature:   Problem Event Name:   APPCRASH   Application Name:   gdb.exe   Application Version:   0.0.0.0   Application Timestamp:   4c87a0eb   Fault Module Name:   gdb.exe   Fault Module Version:   0.0.0.0   Fault Module Timestamp:   4c87a0eb   Exception Code:   c0000005   Exception Offset:   0012a92c   OS Version:   6.1.7600.2.0.0.256.1   Locale ID:   1033   Additional Information 1:   0a9e   Additional Information 2:   0a9e372d3b4ad19135b953a78882e789   Additional Information 3:   0a9e   Additional Information 4:   0a9e372d3b4ad19135b953a78882e789 Read our privacy statement online:   http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline:   C:\Windows\system32\en-US\erofflps.txt Some screenshots with the errors: ---------------------------------------------------------------------- Martin_fr · 2011-08-07 11:11 Lazarus uses GDB in order to debug your app. This is a 3rd party application. For some reason it is crashing on your system. Unfortunately it is not likely this can be fixed in lazarus itself, or by the lazarus team. There is a remote chance that it is caused in combination with you anti-virus solution. Though that usually leads to different errors. You first need to find out which version of gdb is on your system. Find the gdb.exe (options dialog); and run it in a shell. Or (before starting your app) open the"Debug output" window (View menu, "debug windows"), and search for the info there. Other versions (older or newer) may help solving the issue. http://sourceforge.net/projects/mingw/files/MinGW/BaseSystem/GDB/ gdb 7.3 has just been released. It hasn't yet been tested with lazarus, but if you are lucky it solves your issue. AFAIK Laz 0.9.30 was shipped with 7.2.  you may also with to try 6.7.5 or 6.8.3 or 7.01 Note there is also an gbd.exe on your system that was shipped with fpc. I do not know which version that is. And if you upgraded Lazarus over time, you may have an older gdb in use anyway. --- some info on debugging in generic: http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips --- Edit: you may also try and experiment with using either stabs or dwarf. see project options / linking: -g or -gw ---------------------------------------------------------------------- christensen · 2011-08-07 11:40 Here is my GDB version: Quote~"GNU gdb (GDB) 7.2\n" ~"Copyright (C) 2010 Free Software Foundation, Inc.\n" the same security software i use on both OS: Avira Antivir personal edition and Zone Alarm Free. ---------------------------------------------------------------------- BigChimp · 2011-08-07 12:08 You can always raise a bug report. If you add detailed info (compiler versions, lazarus, gdb, as you already mentioned above) and a reproducible test case (example program), that helps a lot. Suppose that the FPC/Lazarus devs can't fix it because it is a gdb issue, at least they can pass the bug report upstream to the gdb people... Good luck! ---------------------------------------------------------------------- Martin_fr · 2011-08-07 13:25 If you do report: here is a list of what best to include in a report: http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#Reporting_Bugs As I said before, if GDB itself crashes, the chances are very slim it can be fixed by Lazarus. Though if it crashes when your app closes, you should have your debugging done => it is an annoyance, yes, but you shuld be able to work. The chances that it will be passed on, IMHO are rather slim too. GDB 7.3 seems in general to be working for Lazarus. just tested that. Don't know if it fixes your issue.. You need to download several dll too. PM me, and I can sent the files