gdb and Lazarus force a hard reboot on Windows 10 64 bit

[EganSolo]

Would love to know how to debug this problem:

Laz 1.4.4 on Windows 10 64 bit. Please note that, at this point, I'm not claiming it's Laz or gdb's problem. It may well be my system at fault. Still, would love to know how to figure out what's going on.

Steps that lead to the hard crash:

1. In Lazarus, start a new application
2. Drop a TFileNameEdit component on the main form.
3. Run the program from within Lazarus. Note that this issue does not surface when I run the program outside of lazarus so I suspect it is related to gdb.
4. Click on the button to open the file dialog window
5. The dialog window appears and before it is fully populated, the program crashes.

The system will either freeze and take down with it the windows explorer subsystem. Ctrl+Alt+Del becomes inoperable. Further, if Task Manager is open and I try to kill the gdb process, task manager becomes inoperable.

At other times, I might get a message telling me that gdb has stopped working.

Any suggestions on debugging this issue would be greatly appreciated.

Thanks

Egan

[Martin_fr]

http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#On_Windows_Open.2FSave.2FFile_or_System_Dialog_cause_gdb_to_crash

Also for 32 bit Lazarus (even on 64 bit system) there is a newer gdb on our sourceforge site.

[EganSolo]

Thanks Martin,

 I disabled the loading of symbols for libraries and I also selected the debug info to Dwarf with sets and the problem is fixed. I will also grab the latest gdb. I think it's well worth it.

Thank you!

[Martin_fr]

its always open/save, because that loads all the shell extensions (icon overlays, context menu handlers, ...) that are installed by other apps on the system.

That is also why the effect differs from system to system. Because it is between fpc, gdb and the 3rd party app.