Answer / ashutosh soni

There are two types of builds: release and debug. Always set
the build type to release for builds that are shipped to
customers. The debug build is frequently used during the
development phase of the application. Both types of builds
can be debugged, and both types of builds must have symbols
to debug them. One important difference is that the release
setting in Visual C++ turns on compiler optimization and the
debug setting turns compiler optimization off. When compiler
optimization is turned on, the application runs faster.
However, it is not as easy to step through the code because
the source code lines are not compiled in the exact order
that they appear in the source code. Therefore, during the
development phase of a project, it is easier to debug a
debug build.

In both the Visual C++ 6.0 and the Visual C++ .NET
development environments, you can create a debug build by
selecting debug as the build type, and you can create a
release build by selecting release as the build type. If you
are not using the Visual C++ development environments, you
must know what compiler and linker options to set.

To enable debugging of a release build for Visual C++ .NET
or for Visual C++ 6.0, change the following compiler options
on the Cl.exe compile of your build:
Compiler

* Enable /Z7 for Visual C++ .NET
* Enable /Zi for Visual C++ 6.0
* Enable /O2

For additional information about the Compiler option, visit
the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/aa236704.aspx
(http://msdn.microsoft.com/en-us/library/aa236704.aspx)
Linker

* Select/INCREMENTAL:NO
* Select /DEBUG:Yes
* Select /OPT:REF
* Select /OPT:ICF

For additional information about the Linker option, visit
the following MSDN Web site:
http://msdn.microsoft.com/en-us/library/aa270751.aspx
(http://msdn.microsoft.com/en-us/library/aa270751.aspx)
Enable Debugging in a Release Build in Visual C++ 6.0
To enable debugging in a release build in a Visual C++ 6.0
development environment, follow these steps:

1. On the Project menu, click Settings.
2. Click Win32 Release configuration.
3. On the C/C++ tab, click General, and then set the
following:
* Set Optimizations to Maximize Speed or to
Minimize Size.
* Set Debug Info to Program Database.
4. On the Link tab, click General, and then set the
following:
* Make sure that you click to select Generate
debug info.
* Make sure that you clear the Link incrementally
check box.
5. Edit the Project options directly, and then add
/opt:ref,icf.

You can now debug your release build application. To find
the problem, step through the code until you find where the
failure occurs, and then determine the incorrect parameters
or code. If a program works in a debug build, but fails in a
release build, it is likely that one of the compiler
optimizations is exposing a defect in your source code.

To create a debug build, use the following options:
Compiler

* Enable /ZI
* Enable /Od

Linker

* /debug
* /incremental:yes

After you have completed the steps, and you recompile the
application, you will have .pdb files in either the \Debug
or the \Release directory of your project, depending on your
build configuration.

Answer / kris

In my last project, we had 8 builds, and i used 2 get build
every week.

ok.

What if the client finds a defect after delivering the product? How will you react and justify?

2 Answers   HeadStrong, IBM, Somany Ceramics,

---

what is hotfix?

12 Answers   CTS,

---

how to prepare test case and test description for job application(like naukri.com)?

1 Answers   Idea,

---

I have to give weights to 5 stones so that using a simple balance and the stone i should be able to weight any number between 1-100

0 Answers   ADP,

---

last week i attended tawant technologies. it may be useful for for u. i could not remember every qustion and answer. . 1. verfification is a. r we buliding the sys right? b. r we buliding the right sys? 2. regeression tetsing a. always can be done automation b.unchanged areas have not been affected c. changed areas have not been affected. 3.Equalent class partition is a.white box tetsing technique b.Black box tetsing technique ........ c.black box .............. 4.arrange order unit testing,integartion, validation, sys tetsting 5.debugging is a.testing activity b. developement activity c........ d......... 6.security tetsting a. bullet prooof...... wrapped s/w b....... 7.smoke testing a..... 8.defect managent tool does not conatin a. b. 9. sys reliability a. 10.user accceptance tetsing is done by a.tester b.developer c.end users d........ 11.which is not static testing technique a.walk through b.inspection c. d. 12.wat is diff b/w? if the s/w isdeveloped by other country if the s/w isdeveloped by ur country? a.culturtal diff b. re allocation resources. c...........no ctrl pf process d........ plz go through these topics.....i am not able to rememeber every qusetion and answers. sorry let me know u ahve any questions.u can add here extra questions. brahma412@yahoo.co.in

3 Answers   Tavant Technologies,

---

hi there… can any1 tel me small testing companies in bangalore to work…I hav learnt testing basics at home..I want to experience d job…watever may b d salary i dont bother..I just want to gain knowledge thanx in advance…

1 Answers  

---

What is pesticide paradox? How to overcome it?

0 Answers  

---

How can a tester ensure that his\her test cases covers all the functionalities of a particular application?

5 Answers   Accenture, Oracle,

---

hi this is sunitha yagnamurthy ...what r the certification in testing and hoe to apply that certificaation and what r the topics we will studying in testing...... please anybody explain that process

3 Answers  

---

How to test a Falsh player scrollings?

0 Answers   Accenture,

---

What is change request & what is the role of Tester in change request ? pl explain with example .

1 Answers  

---

How do you estimate staff requirements?

1 Answers  

---