[cdt-test-dev] Sanity CDT Build 1.2.0.59

[Mathieu Lapensee <lapensee@xxxxxxxxxx>]

Recommendation:      Build can be adopted.
 (Bug 43865 has a workaround.
 Please see the bug report for the workaround)

Results: (Only new defects are shown in the table)

Test	Windows 1.2.0.59	Solaris 1.2.0.59	Linux 1.2.0.59
0	529/529	529/529	529/529
1	p (found bug 43815)	p (found bug 43815)	p (found bug 43815)
2.	p	p	p
3	p	p	p
4	p (found bug 43817)	f  (43865)	f  (43865)
5	p	p	p
6	p	p	p
7	p	p	f (43434)
8	f (43431)	p	f (43431)
9	p (found bug 43819)	p	p

#9 Debugging problems... 
Workarounds: 
        fixed:  43122 workaround (optimization):
set makefile/build properties to use -O0, or remove option.
        fixed:  43372 workaround (seems to happen
only on a few machines) put <projectdir>/Release in the debug configuration
source locations 
        Open: 43431 :For managed projects, debugger
won't stop at a breakpoint in a module class (class in a subfolder) constructor
on linux. Can't debug in any subfolder breakpoints (class and method) in
windows. 
        New:
  43865: Managed Build does not build on Solaris and Linux
        New:  
   43815: Cannot create Managed Project when CDT core and only
Managed Build component are installed.
        New:  
   43817: PE Windows Parser not showing right icon for executable
        New:  
   43819: Exception in Debugger when entering text in Console

Sanity testing assumes your environment is set up with:
       a. JDK 1.3.1 on your path ("java -version")
       b. g++, nm, c++filt is on your path
       c. "gdb -version" = 5.2.1 or 5.3
       d. You run Eclipse 2.1.1 (with or without the -data
argument) 
       e. UseInstall/Update Perspective to get to http://update.eclipse.org/tools/cdt/updates/builds/1.2

Sanity Tests: 
0.  The build passes the Automated Integration Suite
       a. Results are available from http://update.eclipse.org/tools/cdt/updates/builds/1.2/index.html
1.  You can create new projects.
       a. Create a new (Standard Make) C++ project
       b. Create a new (Managed Build) C++ project
2.  You can import existing projects.
       a. Import an existing C++ project (eg. HelloWorld)
from somewhere on disk. 
3.  You can build a Standard Make project.
       a. Ensure that a valid Makefile exists in the project.
       b. Project > Build initiates a build.
4.  You can build a Managed Make project.
       a. Ensure that the Managed C++ Make project was created
to produce (depending on your host) a Cygwin/Linux/Solaris Executable.
       b. Disable Window > Preferences > Workbench
> Perform build automatically
       c. Use New Class Wizard for a class "Foo"
(accept defaults) to create a Foo.cpp and Foo.h file.
       d. In "Foo.cpp", type "main"
then Ctrl-Space to add a template for main().  (Add a trailing newline.)
       e. Project > Rebuild creates the Makefile and
builds an executable. 
5.  Files are parsed for language highlighting, and for Outline View.
       a. Open a CPP file in a C++ project and verify language
and outline view. 
6.  You can edit and save C/C++ files.
       a. Enable Window > Preferences > Workbench
> Perform build automatically
       b. Open a CPP file, modify something, and save.
       c. Saving the file causes an automatic build.
7.  You can use the C/C++ Search mechanism.
       a. Enable indexer for project.
       b. From the Search dialog, find all Class Declarations
named "*" in Workspace.
8.  You can create and run debug configurations.
       a. Make sure you have built (with -g option) a simple
executable. 
       b. Create a new Debug configuration (using GDB/Cygwin
Debugger) 
       c. Set "Break at start of main()".
       d. Run the configuration.
       e. Step over a statement, or run to a break-point.
       f. Run to completion.
9. You can close the session.
       a. If started from the command-line (Unix/Linux),
no messages were produced on the console.
       b. There are no errors in the .metadata/.log file

Cheers,
Tanya, Brent and Mathieu