Intel XENIX 286 Programmers Guide (86) - Tenox.tc

XENIX Programming adb: Program Debugger
The command displays the maps for all segments in the program using information taken
from either the program and core files or directly from memory.
If you have started adb but have not executed the program, the $m command display has
the form
Text Segments
Seg # File Pos
63. 32.
71. 2080.
Data Segments
Seg # File Pos
39. 2736.
Phys Size
2048.
656.
Phys Size
242.
'sample' -File
'core' -File
Each entry gives the segment num ber, file position, and physical size of a segment. The
segment number is the starting address of the segment. The file position is the offset
from the start of the file to the contents of the segment. The physical size is the
nu mber of bytes the segment occupies in the program or core file. The file names to
the right of the display are the program and core file names.
If you have executed the program, the command display has the form
Text Segments
Seg # File Pos
63. 32.
71. 2080.
Data Segments
Seg # File Pos
39. 2736.
Vir Size
2048.
656.
Vir Size
456.
'sample' - Memory
'sample' - Memory
where virtual size is the number of bytes the segment occupies in memory. This size is
sometimes different than the size of the segment in the file and will often change as
you execute the program. This is due to expansion of the stack or allocation of
additional memory during program execution. The file names to the right always name
the program file. The file position value is ignored.
If you give a segment number with the command, adb displays information only about
that segment. For example, the command
$m 63
displays a map for segment 63 only. The display has the form
Segment #= 63.
Type = Text
File position = 32.
Physical Size = 2048.
6-23