Cumbersome warning message with gdb lazarus / 12-Debugger ---------------------------------------------------------------------- franzala · 2020-01-11 21:53 When I debug with gdb, a black window appears after a moment with the following message (in french) "Project name" does not answer with to buttons  Force to quit  or Wait. How could I suppress it? ---------------------------------------------------------------------- valdir.marcos · 2020-01-12 03:07 Quote from: franzala on January 11, 2020, 10:53:09 pmWhen I debug with gdb, a black window appears after a moment with the following message (in french) "Project name" does not answer with to buttons  Force to quit  or Wait. How could I suppress it?What OS and bitness? What Lazarus, Free Pascal and GDB versions? ---------------------------------------------------------------------- franzala · 2020-01-12 16:24 By continuing to search, I have got the same window without being debugging, which seems to exclude that the origin of the problem is gdb. The OS is ubuntu 18.04LTS   64 bits FPC 3.0.4 Lazarus 1.8.2+dfsg-3 but I do not know the version of gdb (it is not in the help of Lazarus); where could I get it? ---------------------------------------------------------------------- Martin_fr · 2020-01-12 16:34 Just to be clear, you get the warning window when: 1) the app is paused at a breakpoint / or during single-stepping 2) the app is running 2a) while the app is starting up in gdb. Once it is gone through any initialization it is fine 2b) any time while the app is running. When the app is paused this is normal. The app can not answer to the window-manager. So the window-manager produces a warning. I have no idea, if this feature can be disabled in the window manager, and if so that will depend on which window manager is in use. If the problem happens, while the app is running, then that is odd. GDB should not slow it down that much. If it is during startup, you can try "DisableLoadSymbolsForLibraries" = true. https://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#gdb.exe_ has_stopped_working . It is possible that gdb takes to long, when loading extra symbols (though very unlikely) Slowdown can also happen if you hit lots of exceptions (even if the debugger ignores them and continues, and they are caught and handled by the app). Or if you have breakpoints that are hit (but have a condition, or auto continue). Though you have to hit such a breakpoint hundreds of times..... ---------------------------------------------------------------------- franzala · 2020-01-13 12:50 It appears mainly during single-stepping when I'm looking if some variables have the value I wanted for instance; but it appeared also at least one time while the application was running and waiting for a hit on one button or another. I never had that previously but I changed my OS recently from mageia to ubuntu and I wonder if it could be  related to that change or more probably with a problem between ubuntu and Lazarus, because it appears up to now exclusively under Lazarus. Did you ever hear from the same problem? ---------------------------------------------------------------------- Martin_fr · 2020-01-13 13:30 Quote from: franzala on January 13, 2020, 01:50:31 pmI never had that previously but I changed my OS recently from mageia to ubuntu and I wonder if it could be  related to that change Different distros come with different window managers pre-installed. (You can always install another one, if you like). This "not responding / wait" alert, is a feature of the window manager. So assuming that ubuntu comes with a diff window-mgr, then yes that would be related to the change. Window managers send signals to all the running apps, all the time. And the apps are supposed to answer. If an app does not answer, then usually something is wrong with the app, hence you get a warning. In the debugger (while stepping) this is normal (annoying, but normal). The app is paused, so it can't answer... The message would also appear if you do long calculations inside an event (in the main thread) without calling Application.ProcessMessages. Because while your code is running (in the main thread), the LCL code that would answer messages does not run. I usually see them when using valgrind. valgind slows down execution. So an app running under valgrind often replies to late. Quoteor more probably with a problem between ubuntu and Lazarus, because it appears up to now exclusively under Lazarus. Well do you debug any apps that are not written in Lazarus? As for none debugging occurrence, check what your app does. Use threads or Application.ProcessMessages. As for none-Laz apps do not get that warning... Well then, they are probably well coded. ---------------------------------------------------------------------- franzala · 2020-01-13 14:44 Well, I will investigate the window manager; I do not debug  apps  written under other EDI than Lazarus. In between, I use a larger form than necessary trying not to use the region where the window is located; I hope I will find a netter solution! Many thanks, I will let you know if I find something.