On Fri, Mar 04, 2011 at 11:33:38PM -0800, Patrick Masotta wrote: > Host: Vista; gdb.exe = Custom built MinGW gdb-7.2-1 > Target: Linux; gdbserver=Ubuntu 8.04 GNU gdb 6.8-debian
[While that works in theory, it's in practice usually better to have maching gdb and gdbserver.] > 1) I've been able to make things work compiling my own cross-debugging > version of mingw32 gdb.exe, it would be very handy if you guys add to > ftp://ftp.qt.nokia.com/misc/gdb/7.2/ the Win-Linux cross-debugging version > w/Python. bugreports.qt.nokia.com would be the place to "officially" ask for a feature. This is an interesting use case by the way. Usually people with the possibility to use Linux do that directly, worst case in a virtual machine, but not using cross-compilation.] > 2) when I launch a debug session GDB ends up looking for the source > files at the working directory (always C:\Qt\qtcreator-2.1.81\) if the > sources are not there I just get an assembler view; not source code. I > solve the problem with a gdb command "cd <my_project_dir>" every time > I run my target or now adding that line to the .gdbinit file, changing > it every time I work on a different project. Can't you guys just pass > that "change dir" gdb directive after launching gdb, changing the > working directory to the current project directory? There is a setting for "Working directory" in your project's run settings. Isn't that honoured? > 3) qt-creator does not save the breakpoints to the project file, it > would be very handy saving them, if not I have to reset breakpoints > every time I start a new debugging session.... Breakpoints are saved in the session. See http://doc.qt.nokia.com/qtcreator-snapshot/creator-project-managing-sessions.html > Last, "how do I do for being able to post at nntp.qt.nokia.com" and > follow this conversation on my news reader ?? No idea, sorry. Andre' _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-creator
