Re: [Ayatana-dev] Debugging Unity-2d QML

[Richard Dale <richard.dale@xxxxxxxxxxxxxxx>]

On Monday, April 11, 2011 02:10:24 PM Ugo Riboni wrote:
> > I was hoping that it would be possible to get the Qt Creator QML debugger
> > to attach to an already running process like the unity-2d-spread
> > process, in a similar way to gdb attaching to a process. It turns out
> > that there isn't an option to do that. So my current plan is to attempt
> > to hack the Qt Creator code to add that feature. My worry is that, even
> > after doing that, I still wouldn't find out what was causing bug
> > #753269. But I can't think of a better plan of attack - does anyone have
> > any suggestions?
> 
> Hi Richard,
> One suggestion I can give you is that instead of trying to attach the
> debugger to a running unity-2d-spread process you can kill the existing
> one (it won't be respawn by the session) and launch a new one via the
> debugger.
Yes, I've been trying that, but unity-2d-spread needs to be run as root. So I 
tried running qt creator as root with 'sudo qtcreator' in my current session 
but that didn't work too well. Or maybe I should set the setuid bit on the 
unity-2d-spread executable so it can run as root - I'm still experimenting.

It doesn't look too hard to add a menu option 'Connect to Running QML 
Application..' to 'Debug -> Start Debugging' to Qt Creator though, and I've 
started doing that now too. Certainly if I need to debug unity-2d-launcher and 
unity-2d-panel I'll need be able to connect to a running process anyway, 
because they must be started by the gnome-session process.

-- Richard