Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PluginFest 2007/MB Nokia"
Line 16: | Line 16: | ||
* What problems did you find | * What problems did you find | ||
** Macrobug problem: Selecting a code item in the historical call stack did not go to the relevant code. This may not be related to the new version of Carbide as I (Adrian) have seen this before. | ** Macrobug problem: Selecting a code item in the historical call stack did not go to the relevant code. This may not be related to the new version of Carbide as I (Adrian) have seen this before. | ||
− | ** Nokia problem: when creating a new project it includes two versions of each file in the Project Explorer. This is | + | ** Nokia problem: when creating a new project it includes two versions of each file in the Project Explorer. This is apparently a known issue with this really early version of Carbide 1.2. |
* What resolutions did you find | * What resolutions did you find | ||
** n/a - everything worked well enough | ** n/a - everything worked well enough | ||
* Is there a screenshot? | * Is there a screenshot? | ||
** Yes | ** Yes |
Revision as of 09:58, 25 January 2007
- Companies
- Participants from Macrobug
- Adrian Taylor
- Participants from Nokia
- Ken Ryall
- Don Podwall
- Products tested and versions
- Nokia Carbide.C++ 1.2 pre-beta
- Macrobug Memory Leak Tracer 1.0.3 pre-alpha
- How did the test go?
- Problems with workarounds
- What tests did you complete?
- Installed Memory Leak Tracer 1.0.3 on a clean installation of Carbide 1.2 alpha on Adrian's laptop.
- What problems did you find
- Macrobug problem: Selecting a code item in the historical call stack did not go to the relevant code. This may not be related to the new version of Carbide as I (Adrian) have seen this before.
- Nokia problem: when creating a new project it includes two versions of each file in the Project Explorer. This is apparently a known issue with this really early version of Carbide 1.2.
- What resolutions did you find
- n/a - everything worked well enough
- Is there a screenshot?
- Yes