Because when you turn off dependency checking, sometimes the build system fails to compile things that need building. If, for example, you have nested header files and change a header included by...

Knowing the exact error message would be helpful. If the space in your workspace path is not a typo, you need to know that the Symbian build system does not support spaces in your path and that is...

"However I cannot use the "TRK 2.x USB" setting in Carbide"

In addition to the information above about TRK 3.0.8 being blocked, this is the wrong connection type for TRK 3.x. Use the "USB" setting...

Carbide v1.0 was exactly what one would expect from a 1.0 software product: lots of new technology that isn't quite stable yet. 1.0 was a promising release but it was of fairly limited usefulness...

Emulator or on-device? And what version and build of Carbide are you running? I'd recommend trying out the new 2.0 release first and seeing if that helps.

Regards,

Matt P.

Sorry that 1.3 isn't behaving for you, but keep an eye out for Carbide v2.0; it's probably worth trying again when the new release is available.

Regards,

Matt P.

What release of Carbide v1.3 are you using? Have you updated to the most recent one, v1.3.2?

Regards,

Matt P.

I would recommend that you create a new Carbide workspace on drive N:, reimport your project, and see if that solves things for you. The Symbian build system does not like having projects on a...

If this is still a problem, do the SDKs show up in the SDK Preferences panel that wizard_hu mentioned? Which kits are not appearing?

Regards,

Matt P.

What version of Carbide are you using, and what SDK? I would start by making sure you're using the latest release, which is v1.3.2.

Regards,

Matt P.

Do you really need to use an S60 2nd edition kit? I highly recommend going with a newer kit if you can. Otherwise Carbide.c++ v1.2 is indeed still available for download here if you require 2nd...

Martin,

1. Yes, some people do use TRK to debug on their boards. It works well, as long as you are aware of the limitations. (For example, it is not possible to debug drivers that are loaded...

CodeScanner is enabled for all varieties of Carbide.c++ v1.3.2, but only the S60 5.0 migration rules for touch screen UIs are supported under the Express version. To access the rest of the...

Can you pull up your Windows task list and see if you have a process named de.exe there? If so, kill it and see if the problem persists.

Regards,

Matt P.

I can't quite tell if this is a general Symbian API question or something Carbide-specific. Which SDK are you using, and which version of Carbide?

Regards,

Matt P.

Can you please submit this through our Bugzilla system so we can get one of the UI Designer engineers involved? We might need to see your project, if that's possible.
...

I'm not sure I understand what you are asking. The lines you showed are a list of what functions are on the call stack, they are not disassembly. Can you provide more details of what the problem is,...

You need to update to the latest TRK, v2.8.9, available in Carbide v1.3.1 build 34. See this thread:

http://discussion.forum.nokia.com/forum/showthread.php?t=134912

Regards,

Matt P.

If you installed Eclipse to a different location than your Carbide.c++ install then the two should not conflict in any way.

It sounds like it's just grabbing whatever comes first in the path. This...

Does anything show up in the TRK connection log, down in the console view?

Also, I'd recommend running the updater; the current release is 1.3.1 build 34.

Regards,

Matt P.

We've been getting a lot of reports of bad info in symbolics generated by GCCE. Can you please tell me what compile settings you changed to get it to work in 1.2?

Regards,

Matt P.

Have you noticed what it was doing when it got stuck? Click on the little treadmill icon down in the right-hand side of the taskbar to see what task is stuck.

Regards,

Matt P.

Hmm. Works fine for me. You're sure it was behaving itself before you upgraded to 1.3.1?

I think we need to get engineering involved in this one. Have you used our Bugzilla system? Please go to https://xdabug001.ext.nokia.com/bugzilla/, create a login, and submit this issue there. We'll...

Please start by upgrading to v1.3 and see if the problem persists.

Regards,

Matt P.