Re: first try of KDevelop 5.0.4
Milian Wolff <[email protected]>
| Newsgroups | gmane.comp.kde.users.kdevelop |
|---|---|
| Message-ID | <1682651.lUgCoQlQgY@agathebauer> |
On Montag, 27. März 2017 22:13:13 CEST René J.V. Bertin wrote: > 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.: What kind of deadlocks are you talking about? This would also indicate issues we are unaware of that need to be fixed. > %> 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. -- Milian Wolff [email protected] http://milianw.de
signature.asc
(application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQQ9hWiGkJfGXJj40nYMDrISzR0TkwUCWNl3DQAKCRAMDrISzR0T k3rJAJ44i1/2YfgwIOso3Xn5SwFfVci+swCgoDldtfQgTEJE5ly/pzfWcYJOjF0= =Jcct -----END PGP SIGNATURE-----