Best Answer

d a tool for analysing c plus plus program

User Avatar

Wiki User

โˆ™ 2010-04-01 22:33:11
This answer is:
User Avatar
Study guides


20 cards

A polynomial of degree zero is a constant term

The grouping method of factoring can still be used when only some of the terms share a common factor A True B False

The sum or difference of p and q is the of the x-term in the trinomial

A number a power of a variable or a product of the two is a monomial while a polynomial is the of monomials

See all cards
1759 Reviews

Add your answer:

Earn +20 pts
Q: Lint is a compiler b a interactive debugger c a cinterpreter d a tool for analysing c plus plus program?
Write your answer...
Still have questions?
magnify glass
Related questions

Main features of turbo c compiler?

Text editor Compiler Linker Debugger

What are turbo c components?

Editor Compiler Linker Debugger

What are the components of turbo c?

Editor, Compiler, Linker, Debugger

Basic parts of turbo c?

Editor, Compiler, Linker, Debugger.

What are the 3 turbo c language components?

Editor Compiler Linker Debugger

What is the mainpart of turbo-c?

It has more than one main parts: editor, compiler, linker, debugger, help-system

What are the cousins of a compiler?

First cousin twice removed is an interpreter, second cousin is an assembler. Its siblings are a text-editor, a linker and a debugger.

Is compiler a system program or an application program?

Programming language compilers are application programs. In some publications, however, the term system software also includes software development tools (like a compiler, linker or debugger).

Is C plus plus an application program?

No. C++ is a computer language. The development system supporting it is a compiler, linker, editor, debugger, etc.No it is a programming language.

Basic parts of TURBO C program?

Editor - edits text Compiler - compiles the program Linker - links the program Debugger - helps finding bugs

When was GNU Debugger created?

GNU Debugger was created in 1986.

If you can debug codewith break point in Release mode then what is actual necessity of Debug mode?

You are confusing debug mode with debug build. A build simply defines a specific set of compiler options to produce an executable. You can define as many builds as you like so you can easily switch from one configuration to the other without having to continually reconfigure the compiler options. For instance, if you are working on a 64-bit machine you might choose to create a separate executable specifically for 32-bit systems, therefore you need a separate build configuration with the appropriate compiler options. A debug build is simply a compiler configuration that is ideally suited to debugging because it has no compiler optimisations and may include source code that will not be compiled in the release build. However, release builds can also be debugged. As developer you will have access to the program debug database, but you can also make this database available to your users if you wish them to be able to debug your release builds. Debug mode is not the same as a debug build. When you run your program from within the debugger (or from within your IDE) then you are in debug mode. In this mode, the program is attached to the debugger and all breakpoints set within the debugger will be honoured, even if it is a release build you are running. But when the program is executed outside of the debugger then you are in standalone (normal) mode and the breakpoints will have no effect, even in debug builds. Your debugger will typically provide some means to execute the program outside of the debugger. In Microsoft Visual Studio, for instance, F5 runs the program in debug mode while CTRL+F5 runs the program in standalone mode. When an exception occurs in standalone mode, the operating system will ask if you want to debug the program or terminate the program. If you choose to debug, then the operating system will ask you to specify your debugger. If the debugger is already running then that will be listed as one of the options but you can choose to use a new instance of the same debugger or choose another debugger entirely (if one is available). Once you select the debugger, the debugger attaches itself to the process and sets up the debugging environment. Provided the program's debug database is available, the debugger will then isolate the problem and present the code to you just as if you'd run the program in debug mode. If the database is not available, the program will be disassembled instead -- you won't have access to the source code.

People also asked