OpenDialog debug error
lazarus / 34-Windows

----------------------------------------------------------------------
Robz · 2015-09-18 01:35

Hi,

I get an error using the opendialog execute command while in the
Lazarus debug mode. However, the openDialog execute command works, as
expected, in the release mode. By contrast, I have no problem using
Delphi XE6 opendialog execute function, in Delphi debug or release
mode.
Using Windows 10 64 bit.

Code used:


procedure TForm1.MenuItem5Click(Sender: TObject);
begin
  with OpenDialog1 do
    if Execute then
      form4.Show;
end;

 Lazarus Debugger Error

"Ooops the debugger entered the error state.
Save your work now !

Hit Stop, and hope for the best, we're pulling the plug.
Could not send a command to GDB.
The GDB process is no longer running."

Help is greatly appreciated.

----------------------------------------------------------------------
Martin_fr · 2015-09-18 02:08

If you compile a 32 bit app then
http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#On_Windows_Open.2
FSave.2FFile_or_System_Dialog_cause_gdb_to_crash


If you compile a 64 bit app, you can try the setting (see link) or you
may need a never version of gdb (we currently do not have a download
for that)

----------------------------------------------------------------------
Robz · 2015-09-18 22:58

QuoteIf you compile a 64 bit app, you can try the setting (see link)
or you may need a never version of gdb (we currently do not have a
download for that)

Thank you Martin_fr.
I will try your suggestion. I should have mentioned that
OpenDialog.execute did work a month ago. Something changed to cause
the error. I have kept all my debugger settings the same. Using
Lazarus # 1.4.2 2015-7-11. I deleted Microsoft Cortana about the same
time as the error appeared. Normally, you have to be a "trusted
installer" to delete certain applications. However I used a Linux USB
thumb drive to boot to Linux and easily deleted "Cortana" and all the
files in the folder. I have not noticed any change with Windows 10,
except Cortana is DEAD!

----------------------------------------------------------------------
Martin_fr · 2015-09-19 01:36

The open (and other file-) dialogs load all the shell-extensions on
your system. (like apps that create context menu entries, or icons
overlays, or other).

Any install or update of an app may add or change those. And then you
may get this behaviour.

Since they are all dll, disabling gdb for libraries usually does the
trick. Even if a dll has no debug info, gdb still analyses entry
points, and I do not know what else.