Stony Brook Modula-2 archive

Code Expressions

Use the following formats to specify code locations. Code locations are used when you view a code location or to describe a breakpoint location.

Module name

Format:	ModuleName
Description:	This form is used only to view a location. The module is displayed starting at line number 1. Note: This can not be used for setting breakpoints, it can only be used for viewing source code.
Example:	ScreenOutput

Line number

Format:	[ModuleName] LineNumber [SourceFile]
Description:	The currently displayed module is assumed unless supplied, and the current source file is assumed unless supplied. If a module has more than one source file, the line number specified can be ambiguous. In these cases you should specify the source file to eliminate the ambiguity.
Examples:	132 ScreenOutput 132 ScreenOutput 132 writestuf.inc

Procedure or function name

Format:	[ModuleName.]ProcedureName
Description:	The current displayed module is assumed unless specified. The location specified is the BEGIN of the procedure.
Examples:	ScreenOutput.WriteString WriteString

Public symbols in Modula-2

Format:	%publicname
Definition:	Public symbols are names that are defined as public in object modules. In Modula-2, the variables and procedures declared in Definition modules are declared as public. This form is useful for referring to global variables in modules that you have not compiled with symbolic debug information. The public symbol name declared in Modula-2 is: ModuleName_SymbolName Hint: If no type information is available the symbol should be coerced to the correct type. Generally, this format is never used in favor of including and using symbolic debug information.
Example:	%SYSTEM_PrefixSeg, %MyModule_MProcedure:MyType

Public symbols in Ada95

Format:	%publicname
Definition:	Public symbols are names that are defined as public in object modules. In Ada95, the variables and procedures declared in library Package specification modules are declared as public. This form is useful for referring to global variables in modules that you have not compiled with symbolic debug information. The public symbol name declared in Ada95 is: ModuleName_SymbolName Note: For Ada95 procedures the compiler uses additional information in the public symbol name for handling procedure overloading. Hint: If no type information is available the symbol should be coerced to the correct type. Generally, this format is never used in favor of including and using symbolic debug information.
Example:	%SYSTEM_PrefixSeg, %MyModule_MProcedure:MyType

Absolute address

Format:	[[segment:]offset] segment and offset are expressions. segment is only applicable to IA-32 processors. @CS is assumed if segment is not supplied.
Description:	This is an advanced feature, and is useful for assembly language debugging or debugging code for which you have no source.
Examples:	[074Ah:23h] [0E7Bh]