Bug in CVariableFactory for globals, the filename of the
binary was use instead of the filename of the symbol.
* src/org/eclipse/cdt/debug/internal/core/model/CVariableFactory.java
Handles Managed Build System projects that fail to open or convert, for example, because the tool-chain that the project uses is not installed.
When a project configuration is removed, cleans the configuration output.
Edits for some of the externalized strings.
Implement new Interface ICDIFunctionFinished.
It returns the return value of the function.
* cdi/org/eclipse/cdt/debug/mi/core/cdi/FunctionFinished.java
* cdi/org/eclipse/cdt/debug/mi/core/cdi/event/SuspendedEvent.java
* mi/org/eclipse/cdt/debug/mi/core/event/MIFuncitonFinishedEvent.java
Fixed 77379[IProblems][line: -1] IProblem with line: -1 in basic_string.tcc (template related?)
Fixed 77382[IProblems][line: -1] 'this->' in basic_string.tcc has invalid IProblem
Fixed 77389[IProblems] no filename associated with IProblem (ambiguity encountered during lookup)
Fixed 77390 [IProblems] no filename associated with IProblem (Invalid arithmetic conversion in file)
Fixed 77391 [IProblems] no filename/message associated with IProblem in list.tcc
Remove option to use an existing class as enclosing type (defer to future release)
* src/org/eclipse/cdt/internal/ui/wizards/classwizard/NewClassCodeGenerator.java
* src/org/eclipse/cdt/internal/ui/wizards/classwizard/NewClassCreationWizardPage.java
* src/org/eclipse/cdt/internal/ui/wizards/classwizard/NewClassWizardMessages.properties
The majority of the code changes were for dealing with the Java class attributes (buildfileGenerator, etc ).
The other bug fixes were:
When the user displays the properties of a file in a standard make file, the C/C++ category is displayed in the left pane I couldnt figure out a way to filter it out. Before the fix, the Managed Make property page was displayed and would then crash when the user selected OK. Now, it displays a label saying that this page only applies to Managed Make projects.
When the user has automatic build set, edits the properties of a configuration, selects a different configuration, selects OK when asked to save the changes, a build for the proper configuration would start but it would pick up the tool settings from the wrong configuration (the newly selected one).
There was a bug in the Option.onlyOverridesValue method where it wasnt checking for a zero-length built-ins list, and therefore returning the wrong answer.
There was a bug in adding a Tool to a ToolChain where the new Tool was added to the toolList but not the toolMap.
