You could always modify /etc/sudoers to allow gdb to be run without a password.
/s/ Adam On Wed, Apr 14, 2010 at 6:56 PM, Bryce Schober <bryce.scho...@gmail.com> wrote: > yep. The problem is that I can't figure out how to get qt-creator to allow > any wrapper to do the interactive stuff necessary to get through sudo, or > preferrably gksu. That said, I'm pretty much a newb. > > On Wed, Apr 14, 2010 at 2:54 PM, Andre Poenitz > <andre.poen...@mathematik.tu-chemnitz.de> wrote: >> >> On Wed, Apr 14, 2010 at 02:28:27PM -0700, Bryce Schober wrote: >> > Neither option works for me. Our application, which is a >> > PC-build-variant of >> > our embedded application, calls mlockall(), which fails with EPERM. >> > Normal >> > command-line usage of sudo works great, either for running or debugging >> > with >> > gdb, but I'm not sure how I would get equivalent permissions through >> > qt-creator. >> >> How do you invoke gdb as a user in that case? >> >> Plain 'sudo gdb'? >> >> Andre' >> _______________________________________________ >> Qt-creator mailing list >> Qt-creator@trolltech.com >> http://lists.trolltech.com/mailman/listinfo/qt-creator > > > > -- > Bryce Schober > > _______________________________________________ > Qt-creator mailing list > Qt-creator@trolltech.com > http://lists.trolltech.com/mailman/listinfo/qt-creator > > _______________________________________________ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
