I recently switched to QT S60 to do my application, but I have some issues with the On Device Debug.
By Searching a little I'm not the only one, but I didn't find any solution.
Here is my dev env :
Symbian sdk 3.2 V1 and 5th 1.0
Last activ perl and python
So here is the issue :
When I run a On Device Debug, it's not possible to use breakpoint. All of them are "unresolved".
step to reproduce :
- create a new QT project with qt main windows or qt widget as project type.
- select sdk 3.2 or 5th (I didn't try any other one, but I presume that the problem will be here too)
- build the configuration (GCCE)
- create a debug config for ODD
- launch it.
- All the breakpoint do you use are unresolvable. (some time in the main.cpp I'm able to place a working one. But there is no use to put a breakpoint in here...).
Here is what I've already checked/tested :
- create a new project without QT to see if the breakpoint works. (it's okay all is fine)
- updated carbide to 2.5.0 (always same, but worst because in 2.5 the qt project file editor had a little bug while adding new files)
- checked the .map file to see if all the files was referenced in it. (yes they are)
- tested on N78 and E71
- Verified the debug config
- In the emulator all is fine.
So someone has any idea about how to fix it ? or did the ODD with GCCE works for someone ?
Some times I also have another strange thing. It's impossible to start the debug. I've got a empty error message about com.nokia.cdt.debug.launch plugin (In the error log of carbide).
Here is the error log :
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments: -os win32 -ws win32 -arch x86
I can correct this second issue by changing the order of the sources files in my *.pro file but the breakpoint are always unresolvable. I put this little issue here because I thing it's perhaps linked with the first one.