Hi Eran,
sometimes when the debugger is invoked you're stuck without user input in CL, wether from a breakpoint or failed assert. F.ex. it happens consistently when the client has mouse capture, I then have to ctrl-alt-f2 to kill gdb. When it happens under LLDB I may have to kill CL altogether.
Is there a way CL could restore user input on debug break? Possibly by having a timer on its alert msg, say if the user doesn't click OK within 15 seconds?
thx a lot & cheers,
-- p
UI lock-up on debugger entry
-
- CodeLite Expert
- Posts: 231
- Joined: Sat Nov 24, 2012 8:04 pm
- Genuine User: Yes
- IDE Question: c++
- Location: Los Angeles
- Contact:
UI lock-up on debugger entry
main: Debian Jessie x64 + custom wxTrunk