On Oct 17, 2010, at 9:21 PM, ext Andre Poenitz wrote: > On Sat, Oct 16, 2010 at 07:13:11PM +0300, Juha Ruotsalainen wrote: >> Hi there! >> >> Can someone more knowledgeable than I give a good answer how to proceed with >> this problem: >> I'm running Ubuntu 10.10 and Qt Creator cannot debug there due to 10.10's >> heightened security. > > *sigh* > >> Currently I can debug with: >> a) sudo qtcreator (don't like this) >> b) First echoing 0 to /proc/sys/kernel/yama/ptrace_scope then running >> qtcreator > > Is any of that needed when using plain gdb?
>From https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening I would think that only attaching to an arbitrary process should be blocked (for both Qt Creator and plain gdb), normal debugging from Qt Creator (i.e. starting the debugged process from Qt Creator) should still work (except perhaps for debugging an application that is "run in a terminal", since in this situation we explicitly "attach" gdb to the app that is run in the terminal). ++ Eike >> I'm looking for a solution where I could launch qtcreator without any extra >> gimmicks. >> Would setting setuid bit for qtcreator cut it? >> >> Oh, I also tried setcap cap_sys_prace=eip qtcreator but that didn't work >> because >> qtcreator cannot find libextensions. If I change the 'eip' to plain 'i', >> qtcreator starts >> but still debugging results in 'Ptrace: not permitted'. >> >> Any ideas? > > Ask the distributor? > > Andre' > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-creator _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
