>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.]
>

I'm not cross-compiling, "I'm cross-debugging", I'm porting a console windows 
app to Linux then I do as much as I can in Visual Studio then I compile in a 
Linux VM but the final debugging without a graphic environment is a pain, 
qt-creator could be a very good tool for the cross-debugging scenario. 
Cross-debugging Android is another very interesting scenario for qt-creator....

> > 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?
>  

when I run my app I use
Debug/Start Debugging/Start and Attach to Remote Application../
then I'm asked for;
Debugger:______
Local Executable:____
Host and Port:____
Architecture:____
GNU Target:___
Sysroot:___
but ther's not an option for local directory (where the sources are), then gdb 
just take the qt-creator (invoking app) default's directtory as the current 
working directory, it is a pain.
Another thing related to this is that qt-creator shoud remember the run 
parameters in a project base not in a global base, even if I have not a loaded 
project in the IDE if I invoke 
Debug/Start Debugging/Start and Attach to Remote Application.../
the last used parameters are loaded as default, I think that info should be 
stored in the project file and loaded with it...

> > 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
> 
in my humble opinion I think the "sesion" file should be the project file 
itself, here Visual Studio does a good job. Why to split the project data on a 
project file and a "sesion" file independently handled??? I don't know, am I 
missing some point here?


please some one tell me how I have to do to be authorized for posting on the 
news group....

thanks
Pat




      
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt-creator

Reply via email to