https://bugs.kde.org/show_bug.cgi?id=368603
--- Comment #22 from Aetf <7437...@gmail.com> --- For a simplest session: $ lldb-mi /path/to/executable -break-insert main.cpp:30 -exec-run There are also commands like -exec-continue, -exec-next. Reference: https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Program-Execution.html#GDB_002fMI-Program-Execution I don't have enough knowledge about how actually a debugger scans app's memory space or the overcommit thing. But my intuition is, just attaching a debugger to the app shouldn't dramatically increases its memory usage... AFAIK, starting a complex app in debugger takes longer simply because the program is being instrumented and thus runs much slower. -- You are receiving this mail because: You are watching all bug changes.
