[Linux] Debugger error

[matthijs]

Could you pull this plug?  
(http://willemstein.net/images/debugger.jpg)
I've configurred Lazarus to use the standard gdb. I'm using a csv build of this morning but had the same with a csv build of a few days back.

While I'm at it, pressing ctrl-f2 to reset my running program doesnot work. I'm using KDE with multiple desktops and ctrl-f2 switches to desktop 2 (as ctrl-f1 switches to desktop 1, etc etc. )

[Marc]

This can sometimes happen when the lazarus interface to gdb got an unexpected result.
After clicking OK, the gdbprocess is killed. However this may not always work.
From the menu Run-> reset debugger you can manually reset the debug process.

About the keys:
We cant capture keys handled by the OS/WM

[matthijs]

After clicking OK, the gdbprocess is killed. However this may not always work.
From the menu Run-> reset debugger you can manually reset the debug process.

Tried that off course. Didnot work though. Tried restarting Lazarus as well, didnot work either. Only thing to get my project running within the IDE was disabling debugging, by removing the debugger path from the options.

About the keys:
We cant capture keys handled by the OS/WM

I understand that. That not why I reported it. I thnik we might want to rethink some used shortcuts. As I like to work as much as possible with the keyboard.

[Marc]

debugger:
did you include debug info ?
did you not strip symbols
did you not use UPX or something similar
did you not use a runing applications (see run parameters)

keys:
you can customize all keys in lazarus.

[Lightning]

Marc, i still have problems on XP with GDB, it's simply too unstable even after installation with the first project you get GDB SIGSEGV, either Lazarus has some memleaks or GDB itself.
Maybe it's more stable on Linux.

[Marc]

The version of gdb to use on windows is very version dependent
You may experiment with the various cygwin/mingw versions available on the net.