 CARM User's Guide Discontinued | |
| Home Products Events Support | |
Technical Support
On-Line Manuals
CARM User's Guide
CARM Introduction Compiling Programs
Environment Settings Command Prompt ERRORLEVEL Output Files Listing (LST) File Preprocessor (I) File Object (OBJ) File Source (SRC) File Directives Reference ARM BIGENDIAN BROWSE CODE COND DEBUG DEFINE EJECT FLOAT64 INCDIR INIT INTERWORK LISTINCLUDE NOALIAS NOCOND NOEXTEND NOINIT NOINTERWORK NOOBJECT NOPRINT OBJECT OPTIMIZE PACK PAGELENGTH PAGEWIDTH PREPRINT PREPRINTONLY PRINT RESTORE SAVE SIGNED_CHAR SYMBOLS TABS THUMB USERCLASS WARNING WARNINGLEVEL Language Extensions Preprocessor Advanced Programming Error Messages Library Reference AppendixDEBUG Compiler Directive
| Abbreviation | DB | |
| Arguments | None. | |
| Default | No Debug information is generated. | |
| µVision | Options — Output — Debug Information. | |
| Description | The DEBUG directive instructs the compiler to include debugging information in the object file. By default, debugging information is excluded from the generated object file. Debug information is necessary for the symbolic testing of programs. It contains global and local variable definitions and their addresses, function names and addresses, and line number information for source code. Debug information contained in each object module remains valid through the Link/Locate process and may be used by the µVision debugger or by an emulator. | |
| Example |
CA SAMPLE.C DEBUG #pragma db |
| Contact Site Map Press Privacy | Copyright © 2008 Keil™, An ARM® Company. All rights reserved. |
