diff -r f330c1e8a4f3 -r 6b79ffb176c5 carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/html/gettingStarted/launchconfig.htm --- a/carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/html/gettingStarted/launchconfig.htm Wed Mar 25 11:55:19 2009 -0500 +++ b/carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/html/gettingStarted/launchconfig.htm Fri Mar 27 10:36:17 2009 -0500 @@ -4,18 +4,26 @@ Debugging a Carbide.c++ plug-in +

Debugging a Carbide.c++ plug-in

In order to launch Carbide.c++ in debug mode you need to create an Eclipse runtime debug configuration. Follow these steps.

  1. Click the Debug icon () in the task bar or right click on a project and choose Debug As > Open Debug Dialog... You should see the Eclipse launch configuration dialog.
    2. -
  2. Choose Eclipse Application and then click on the New button. A new configuration is created. You should be able to take the default settings which should look like this:
    +
  3. Choose Eclipse Application and then click on the New button. A new configuration is created. You should be able to take the default settings which should look like this:

    -
    +
    4. -
  4. Click Debug and you should have a fully functional debug environment around Carbide.c++.
    -
    5. +
  5. Click Debug and the Carbide.c++ project will launch another instance under debug control. You can set breakpoints in any of the plug-ins you have imported or any sources in the stack crawl during a debug session.
    +
    +
    + TIP: Under the Arguments Tab, be sure to add theses VM Arguments for memory management: -Xms40m -Xmx1024m
    +