[cdt-dev] Sanity results for CDT Build 2.0.0.200404011349

[Brent Nicolle <bnicolle@xxxxxxxxxx>]

Recommendation:     Build is
recommended to be adopted for more
testing.  Several minor issues found.

Results:

	Windows 2.0.0.200404011349  (Sun JRE 1.4.2)	Linux 2.0.0.200404011349 (Sun JRE 1.4.2)
0	699 tests, 0 failures	see Windows
1	Pass	57134 (GTK): Cut off textbox in New Project Wizard 57142: Empty Make Builder tab in Standard Make project properties
2	Pass	Pass
3	Pass	Pass
4	Pass	Pass
5	57126 - Changing the binary parser from Elf to PE does not always affect existing binaries	57146: NPE on BuildConsolePage.propertyChange
6	Pass	Pass
7	57125 - [Search] When the Search view has focus, the CDT Search menu becomes the Java Search menu 57121 - [Search] Searching when all of the "Search For" checkboxes are unchecked causes an exception	57139: Search won't find things after #include <iostream> 57145: Search does not find moved files
8	(existing issue, partially fixed) 50221: Editor marker bar does not display new breakpoints; still need to see the little blue gif, but at least users can see breakpoints being added.	(existing issue, partially fixed) 50221: see Windows
9	(existing issue) 55149: ScannerConfig messages in log file 57128 - NPEs when exiting from build 200404011349	(existing issue) 55149: see Windows

Notes: 
None at this time

Sanity testing assumes your environment is set up with:
a. Sun JDK 1.4.2_02 on your path ("java -version") 
b. g++, nm, c++filt is on your path 
c. "gdb -version" = 5.2.1, 5.3, or 6.0
d. You run Eclipse 3.0.0.200403261517 (M8 build) (with or without the -data
argument) 
e. Use Install/Update Perspective to get to http://update.eclipse.org/tools/cdt/updates/builds/2.0

Sanity Tests:
0.  JUnit Test Results
1.  Creating new standard/managed C/C++ projects
2.  Import existing projects. 
3.  Automatic building of a project. 
Reminder: 
4.  Building a managed make project. 
5.  Building a standard make project.
6.  Files are parsed for language highlighting, and for Outline View.
7.  C/C++ search from the Search dialog. 
8.  You can create and run debug configurations. 
9.  Close the session and look for silent failures captured in the
.metadata/.log file.