Using OpenDialog to add lines to DBMemo crashes debugger in Lazarus
lazarus / 12-Debugger

----------------------------------------------------------------------
bill0287 · 2014-01-02 19:16

See attached project.

If I add an OpenDialog component to the project, press F9, execute the
dialog in some way, and then close the running application I get a
"gdb.exe has stopped running error".  No problems with the project
until the opendialog component is added.

Could this be a bug?

Lazarus 1.0.14 32-bit FPC 2.6.2 running on Win7 64-bit.

----------------------------------------------------------------------
Martin_fr · 2014-01-02 19:32

Most likely a bug in gdb.

on 64 bit the open dialog can also trigger the "SEH" (search forum)
issue, but that is unrelated.

Most likely http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#gdb.e
xe_has_stopped_working

If that does not help, see end of the above page, for how to get a
logfile.

----------------------------------------------------------------------
bill0287 · 2014-01-03 04:51

Using the above link, placing the following string in the
Debug_Startup_Options prevented the error message from appearing.

--eval-command="set auto-solib-add off"

It's worth noting that I had never encountered this problem until I
used the OpenDialog component on the form.

----------------------------------------------------------------------
Martin_fr · 2014-01-03 12:35

Using open dialog means a lot of windows and 3rd party dll are opened.
(any shell add on, icon or context menu handler...). GDB will check
them all.

The line you added prevents gdb from looking for debug info for those
dll.

Apparently on your system one of the dll, has some data that gdb can
not handle.