Re: first try of KDevelop 5.0.4
René J.V. Bertin <[email protected]>
| Newsgroups | gmane.comp.kde.users.kdevelop |
|---|---|
| Message-ID | <[email protected]> |
On Monday March 27 2017 21:57:43 Milian Wolff wrote: > gdb kdevelop > (gdb) run -s <your session> > # wait until everything has finished initialization > # i.e. just before you are about to run your application > # interrupt GDB by pressing Ctrl + C in the CLI, then type: This should work but depending on how large your session is you may win a lot of time, possibly even avoid deadlocks by attaching to the kdevelop session once it's fully started, has done its parsing run etc.: %> kdevelop -s $sessionID & (or kdevelop --ps &) Note the pid printed by the shell. Once KDevelop is idle, attach: %> gdb --pid=$pid Then continue with Milian's instructions: > (gdb) set follow-fork-mode child > (gdb) continue > # now launch your process via kdevelop R.