On Friday 10 December 2010 18:52:57 Berthier, Emmanuel wrote: > I have experiment some solutions: > o Use a remote debugging method based on osc, gdbserver and Anjuta > as gdb frontend: + I can easily recompile module using osc > + I can debug the app using Anjuta > - but I can not easily debug dynamically linked libraries > (as RootFS generated by OSC only contains 1 project) - Anjuta Project > backend is not compatible with Qt projects (Dependency Loop detected in > makefile generated by qmake4) o Use a local debugging method based on gdb > and debug packages: + I need to download/install many debug packages using > zipper - I can not recompile a module > - gdb provide poor source level debugging experience > o Use a remote debugging method based on remote X session, ddd and > debug packages: - I need to recompile ddd for Meego. > + I need to download/install many debug packages using > zipper - I can not recompile a module > + ddd provide good source level debugging experience > o Use a JTAG based debugger (ITP/Lauterbach probe): > + I need to download/install many debug packages using > zipper - I can not recompile a module > - JTAG break points halt the IA core and so interfere with > some realtime system features. + T32 provide good source level and > assembly level debugging experience
I have no experience with Anjuta, but I have used eclipse to debug a remote target with gdbserver. Eclipse provides a powerful front end for gdb, the issue with MeeGo is that the qt plugin from Nokia doesn't work well with eclipse helios. -- Bogdan Cristea http://sites.google.com/site/cristeab/ _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
