diff -r 2c1a7d3f4ab4 -r 24ac5a5cf80c 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 Tue Jul 27 15:20:28 2010 -0500 +++ b/carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/html/gettingStarted/launchconfig.htm Tue Jul 27 15:28:19 2010 -0500 @@ -1,30 +1,30 @@ - - - - -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. -
  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. -
  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
    -
  6. -
- - + + + + +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. +
  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. +
  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
    +
  6. +
+ + \ No newline at end of file