Table of Contents
Advertisement
If you change @as to a value between 4 and 7, the CALLM instruction will
copy arguments from the current stack to the new stack specified in the
module descriptor.
The simulated CALLM instruction puts an undefined value in place of the
saved access level in the module call stack frame. (Normally the saved access
level would have been the current access level, obtained from CPU space
address $10000.)
Using a Hewlett-Packard C Cross Compiler
Use the default compile mode when compiling your target programs for use
with the debugger. The default settings generate executable files (.x file
extension) in the HP-MRI IEEE-695 file format required by the debugger.
The default option settings force a stack frame to be built for every function
call, which is required for stack backtracing.
The "Getting Started" chapter of the Motorola 68000 Family C Cross Compiler
User's Guide gives an example of how to compile a simple program and
execute it in the debugger/simulator environment.
Note
Do not use the –h option when compiling and linking your program for the
debugger. The –h option causes the compiler to generate HP 64000 file
formats. Use the default settings which generate executable files in the
HP-MRI IEEE-695 file format required by the debugger. The debugger
extracts all symbolic information from the executable (.x) file.
Using Environment Dependent Files
The HP B3640 Motorola 68000 Family C Cross Compiler provides
environment dependent files that support the HP B1466 68000-Series
Debugger/Simulator environment. These environment dependent routines
affect the following areas of C programming:
•
•
•
program setup
dynamic memory allocation
program input and output
Chapter 3: Loading and Executing Programs
Compiling Programs for the Debugger
73
Advertisement
Table of Contents
