OS/2 Shareware BBS: 10 Tools/10-Tools.zip/sd386v50.zip/sd386src.zip/SD386.MSG

OS/2 Message File | 1996-08-23 | 53KB | 1,211 lines

MKMSGF
2K3u3
<p=)>
@!BgC
InJjKVL
UlVRW
aSfZk
p%u(u+u
wNyny
sd386.msg
 No help for this item.
SD386 Ver 5.00 08/23/96
  Syntax:   SD386  [Options]  [Program Name] [Program Arguments]
  Options:
  /h or /?      = Print this help screen.
  /p            = Read SD386.PRO.
  /c            = Force case sensitivity for public names.
  /i            = Debug initialization code.
  /f            = Run debuggee in full screen session.
  /w            = Run debuggee in text window session.
  /k            = Keyboard only (no mouse).
  /u            = Do not flush keyboard buffer.
  /m            = Resolve imports.
  /o[Filespec]  = Make a phone line connection to a remote esp.
                  (See notes regarding optional Filespec.)
  /r[n]         = Remote debug:
                      n=0   1    2    3    4    5     6
                  speed=300 1200 2400 4800 9600 19200 38400
  /an           = Which Com(Async) port. For example, /a1 uses COM1:
  /s            = Don't stop at "main" entry point.
  /e            = Use DosExecPgm() to start the debuggee.
  /b[@]Filespec = Debug the child process specified by Filespec.
                  If Filespec is prefixed with @, then debug all the
                  processes specified ( one per line )in the file.
  /nAname       = Remote debug over a netbios connection. Aname is
                  any logical name. Use the same name on both the debug
                  and the probe machine.
  /x            = Disable Ctrl-Esc and Alt-Esc. If abnormal termination
                  leaves Ctrl-Esc and Alt-Esc disabled, then SD386 /x
                  will turn them back on.
  /tname        = Remote debug over a TCP/IP connection. The name is the
                  network name of the machine running the debug probe(esp).
                  The name must be defined in your TCP/IP HOSTS file.
Program Name      = Debuggee EXE name.
Program Arguments = Arguments for the debuggee program.
Notes:
 FileSpec used with /o option:
  Filespec is a file of AT commands that you can send to your
  modem if you want to set modem options not automatically set by
  SD386.
ESP Ver 5.00 08/23/96
Use ESP to establish a null modem or a modem connection to SD386.
 Syntax:  esp [/option]
OPTIONS:
  /r[n]        = Remote debug:
                     n=0   1    2    3    4    5     6
                 speed=300 1200 2400 4800 9600 19200 38400
  /an          = Which Com(Async) port. For example, /a1 uses COM1:
  /o[Filespec] = Read commands in FileSpec and send to modem.
                 (See notes regarding optional Filespec.)
  /nAname      = Remote debug over a netbios connection. Aname is
                 any logical name. Use the same name on both the debug
                 and the probe machine.
  /t            = Remote debug over a TCP/IP connection.
Notes:
 FileSpec used with /o option:
  Filespec is a file of AT commands that you can send to your
  modem if you want to set modem options not automatically set by
  ESP.


  File Pulldown

 Get Function...
  Locates the source file for a function.
 Get Address...
  Locates an address.
 Get File...
  Opens a source file.
 Find Function
  Locates the source file for a function.
 Find Exec Line
  Locates the current execution line.
 Next File
  Gets the next file in the source file ring.
 Drop File
  Drops the current file from the source file ring.
 Browse File...
  Browses a file.
 Restart
  Restarts the target application.
 Quit
  Ends the debugger.


  Get Function

Locates the source file that contains the definition of the
function you specify and adds the source file to the ring of
source files.
Enter the name of the function to locate.


  Get Address

Locates the source file and line number containing the specified
address and adds the source file to the ring of files. If source
is not available then a disassembly view will be shown.
Enter the address you want to go to.


  Get File

Locates the file specified looking first in the ring of files
and then in the list of files linked with the /CO or /DE debug
option.
Enter the name of the file to locate.


  Find Function

Locates the source file that contains the function on which the
cursor is placed and adds the source file to the ring of source
files.


  Find Exec Line

This function brings the currently executing line (Exec Line) into
view and places the cursor on that line.  If the cursor is already
on the Exec Line, then this function will take you to the next line
to be executed in the previous stack frame and place the cursor on
that line.  Subsequent executions will continue to to take you to
previous stack frames until you return to the Exec Line.
Effectively, this function lets you walk the stack in a ring like
fashion adding a file for each stack frame to the ring of files.


  Next File

Switches to the next file in the ring of source files.


  Drop File

If the current file does not define the currently executing
procedure, then Drop file will remove the file from the ring of
files.
  Browse File
Loads a file for browsing.
Enter the name of the file to be browsed.


  Restart

Reloads and restarts the target application.  Breakpoints and
the contents of the data window are retained.
  Quit
Ends the debugger.


  Run Pulldown

 Run
  Runs the target program.
 Single Step
  Executes the current line.
 Step Into
  Steps into a function call.
 Run To Cursor
  Runs up to the cursor line.
 Run              NoSwap
  Runs the program, no screen swap.
 Single Step      NoSwap
  Executes the current line, no screen swap.
 Step Into        NoSwap
  Steps into a function, no screen swap.
 Run To Cursor    NoSwap
  Runs up to the cursor line, no screen swap.
 Set Exec Line
  Sets current line as the next executable.


  Run

Runs the program until a breakpoint is hit, an exception occurs,
or the end of the program is reached.


  Swap

Sets the swap option to swap screens with the target program.


  No Swap

Sets the swap option to not swap screens with the target
program.


  Single step

Executes the current source line (as defined by your compiler).
If the current line calls other procedures, they will executed
but will not be traced.  Use the "Step Into" function to trace
calls to other procedures as well.


  Step Into

Executes the current source line.  If the current line calls
other procedures, they will also be traced.


  Run To Cursor

Sets a one-time breakpoint on the line containing the cursor and
executes the program.  If the cursor line is not hit during the
run, a one-time breakpoint is set on the line to be hit on the
next run.


  Run NoSwap

Runs the program in the background until a breakpoint is hit, an
exception occurs, or the end of the program is reached.


  Single Step NoSwap

Executes the current source line (as defined by your compiler)
in the background.  If the current line calls other procedures,
they will executed but will not be traced.  Use the "Step Into
NoSwap" function to trace calls to other procedures as well.


  Step Into NoSwap

Executes the current source line in the background.  If the
current line calls other procedures, they will also be traced.


  Run To Cursor NoSwap

Sets a one-time breakpoint on the line containing the cursor and
executes the program in the background.  If the cursor line is
not hit during the run, a one-time breakpoint is set on the line
to be hit on the next run.


  Set Exec Line

Sets the current execution line to the line containing the
cursor.
 Set/Clear on Cursor
 Set Conditional on Cursor...
 Set Function Name Break...
 Set Address Break...
 Set Deferred Break...
 Set Address Load Break...
 Set DLL Load Break...
 Clear All Breaks
 Save Breakpoint File
 Restore Breakpoint File
 Edit Breakpoint File
 Hardware Debug Regs...
Sets or resets a breakpoint on the executable line selected by the
cursor.  Highlighted lines denote the executable lines.
Sets a conditional breakpoint on the executable line selected by the
cursor.  Highlighted lines denote executable lines.
Enter a conditional breakpoint expression. The form for the
expression is:
           <variable> <op> <constant>
where
           <variable> is a storage address or a variable name
           <op> is <, >, ==, !=, <=, >=
           <constant> is a constant expression
Sets a breakpoint at a function entry using the syntax
[dllname.]funcname.  If you do not dot qualify funcname and
funcname is not found, then you will be given the option of
deferring the breakpoint for ALL dlls.
Enter the name of the function optionally dot qualified with
a dll or exe name.
Sets a breakpoint on a given address.
Enter the address at which the breakpoint is to be set.
Clears all breakpoints in the target program.
Brings up the watchpoint menu allowing you to enter
expressions for up to 4 watchpoints.  These watchpoints use the
hardware debug registers of the Intel chip.


  Set Data Breakpoint

Sets a hardware data breakpoint at the cursor line.  This
function is currently not implemented.


  Search Pulldown

 Find...
  Finds a specified string in the current source file.
 RepeatFind
  Repeats the prevoius find command.


  Find

Find searches the current source file for a string.


  Repeat Find

Repeats the find command with the previous string entered.


  Data Pulldown

 Show Var
  Shows the value of the variable at the cursor.
 Show Var->
  Shows the contents of the pointer variable

     selected by the cursor.
 Watch Var
  Adds the variable to the data window.
 Watch Var->
  Adds the contents of the pointer variable

     to the data window.
 Expand Var
  Expands the variable in the data expansion window.
 Edit Expression
  Edits the expression.
 Edit Storage
  Edits the storage displayed in the data window.
 Format Var
  Shows action bar of choices for the format of

     the display of the data.
 Remove Var
  Removes a variable from the data window.
 Insert
  Inserts a variable in the data window.


  Show Var

Shows the value of the variable selected by the cursor.


  Show Var->

Shows the contents of the pointer variable selected by the
cursor.


  Watch Var

Adds the variable selected by the cursor to the data window.


  Watch Var->

Adds the pointer variable selected by the cursor to the data
window.


  Expand Var

Expands the view of a variable such as a member of a structure
or union.  If the member is a structure or union, its components
will be displayed in the expansion window.  If the member is a
pointer to another structure, etc., the contents of the variable
pointed to by the pointer will be displayed in the expansion
window.


  Edit Expression

Allows you to edit the expression (formula) which defines what
is displayed by SD386.  One you have changed the expression,
press Enter to cause SD386 to handle the expression or press Esc
to leave the expression alone.


  Edit Storage

Allows you to edit the value of the storaged displayed by SD386.
Once you have changed the value, press Enter to alter the actual
contents of memory or press Esc to leave the contents alone.


  Format Variable

Formats a varible in the data window according to the format
specified.  A menu will be displayed to choose default formats
or enter the format type of the variable.


  Remove Var

Removes the variable selected by the cursor from the data
window.


  Insert

Inserts the variable selected by the cursor in the data window.


  View Pulldown

 Source
  Switches to source view.
 Assembler
  Switches to assembly view.
 Data
  Switches to the data window.
 Data Show/Hide
  Display/Hide data window.
 Timed Show App
  Shows the application screen for few seconds.


  Source

Switches to the source view.  This option is disabled if the
current view is already the source view.


  Assembler

Switches to the assembly view.  This option is disabled if the
current view is already the assembly view.


  Data

Switches to the data window. This option is disabled if the
current window is already the data window.


  Data Show/Hide

This command toggles between showing and hiding the data window.
The contents of the data window remain unchanged.


  Timed Show App

This command shows the application screen for a few seconds. It
returns back to the previous view.


  Settings Pulldown

 Colors
  Sets colors for various screen items.
 Exceptions
  Sets various exception notifications.
 Assembler
 Source
  Sets type of assembly view.
 Mnemonics
  Sets the disassembly option.


  Colors

Sets the colors for the various screen areas.  You can choose
colors, reset to default colors, and optionally save color
settings.


  Exceptions

Allows you choose whether to be notified or not for various
processor and operating system exceptions.


  Assembler
 Source

Sets the assembler view option.  This option toggles between
mixed source/assembly and assembly only views.


  Mnemonics

This command sets the type of disassembly.  This option toggles
between Intel and AL/86 instructions.


  Misc Pulldown

 CallStack
  List of active procedures.
 Processes
  List of active processes.
 Threads
  List of active threads.
 Dlls
  List of dlls for the application.
 Registers
  Register display.
 Edit Registers
  Modify register contents.
 Coprocessor Regs
  Coprocessor register display.


  Call Stack

This command displays the list of active procedures and allows
you to unwind the call stack to a selected procedure.


  Threads

Displays the status of all active threads and allows you to
examine and/or modify their current status.


  Dlls

Displays the list of Dynamic link libraries used by the target
application.


  Registers

Displays the processor registers and their values.  This list is
updated at each instruction step.


  Edit Registers

This command allows you to edit the contents of the registers.


  Coprocessor Regs

Displays the coprocessor registers, stack, and their values.
This list is updated at each instruction step.


  Help Pulldown

 General help
  Display general information about SD386.
 Keys help
  Display the various key assignments.


  Key assignments

SD386 provides a set of default accelerator key assignments.
These accelerator keys can be used in conjunction with the mouse
or by themselves to perform the SD386 functions.  The
accelerator keys can be reassigned in the SD386.PRO file.


  Colors

Mouse Input
Key Input
 If you want to
 Left Click
 Select a window/area definition
 Move &
<- ->
 Move to next field
 Left Click
or Tabs

<BgNext> or
Space
 Switch to next color for background
 Left Click


<FgNext> or
Space
 Switch to next color for foreground
 Left Click


<Default>
D
 Set all of the color selections to defaults
<Reset>
R
 Reset single color selection to default
<Save>
S
 Save current color selections to profile
<Enter>
Enter
 Accept current color selections
<Cancel>
Esc
 Exit without any action
<Help>
F1
 See this Help panel
Enter the string to be searched.  Blanks are allowed in the
string.


  Threads

Mouse Input
Key Input
 If you want to

 Highlight a thread
<Select>
Space
 Select highlighted thread
<Names>
A
 Toggle state, filename, line#, and function info
<Freeze>
F
 Freeze highlighted thread
<Thaw>
T
 Thaw highlighted thread
<Freeze All>
R
 Freeze all threads
<Thaw All>
H
 Thaw all threads
<Enter>
Enter
 Accept current thread status
<Cancel>
Esc
 Exit without any action
<Help>
F1
 See this Help panel


  Exceptions

Mouse Input
Key Input
 If you want to
 Left Click
 Select an exception
 Move &
<- ->
 Move to next field
 Left Click
or Tabs

<Next> or
Space
 Switch to next notification option
 Left Click


<Default>
D
 Set all exception notifications to defaults
<Reset>
R
 Reset single exception notification to default
<Save>
S
 Save exception notifications to profile
<Enter>
Enter
 Accept current exception notifications
<Cancel>
Esc
 Exit without any action
<Help>
F1
 See this Help panel


  Watchpoints

Mouse Input
Key Input
 If you want to

 Select a watchpoint

<- ->
 Tab to next field

or Tabs

<Size>

 Set size of expression (1, 2, or 4 bytes)
<Scope>

 Set scope of expression (local or global)
<Type>

 Set access type (Write, Read/Write, or Execute)
<Status>

 Set status (Enabled or Disabled)
<Enter>
Enter
 Put in the watchpoints
<Cancel>
Esc
 Exit without any action
<Help>
F1
 See this Help panel
 - The Expression must evaluate to a size of 1,2 or 4 bytes.
 - An '*' before the address field indicates SD386 aligned address.


  Call Stack

Mouse Input
Key Input
 If you want to
 Left Click
 Select a procedure
<Get View>
Enter
 View the selected procedure
<Run To>
Alt-Enter
 Resume execution & stop at the selected procedure
<Show All>

 Unwind the call stack using a more rigorous


 algorithm
<Show Named>

 Show call stack, including only named procedures
<Cancel>
Esc
 Exit without any action
<Help>
F1
 See this Help panel


  Browse

           Cursor down one line.
           Cursor up one line.
 PgDn        Scroll down.
 PgUp        Scroll up.
 Ctrl-PgDn   Bot of screen.
 Ctrl-PgUp   Top of screen.
 Ctrl-Home   Top of file.
 Ctrl-End    End of file.
 / or F      Find.
 R           Repeat find.
 Esc         Leave browse.
 F1          Help.
Any data type may be specified.  SD386 will prompt you for a
type name.  The variable will be formatted as indicated by the
type (char, int, long, uchar, uint, ulong, float, double, or
@mytype).  "@mytype" tells SD386 to format the variable as the
type of the variable "mytype."  The variable you choose must be
known to SD386.  You may add an asterisk (*) after any of the
types to indicate a pointer to that type.
Data is shown as hex bytes.
Data type is CHAR (8 bits).
Data type is SHORT (16 bits).
Data type is LONG (32 bits).
Data type is FLOAT (32 bits).
Data type is DOUBLE (64 bits).
Data type is the actual data type of the variable as defined in
your program.


  Formula Edit


 Type the new formula for this line, then press
. Press Esc to
 recover  the  old  formula  for this line. Formulas are simple C
 expressions using variable names, constants, register names, and
 the operators + - * . -> [] and :.

 Some example formulas are:

   buffer+20    20 bytes beyond buffer.
   ss:sp        The top of the stack.
   *root        The data pointed to by root.
   table[10]    The 10th element of the table array.
   node.p->id   The id field of the struct pointed
                to by the p field of node struct.

 One or more * or one & may appear at the beginning of the
 formula, and is evaluated last.

Enter a tag name or a typedef.
Enter a number from -128 (0x80) to 127 (0x7F).
Enter a number from 0 (0x0) to 255 (0xFF).
Enter a number from -32768 (0x8000) to 32767 (0x7FFF).
Enter a number from 0 (0x0) to 65535 (0xFFFF).
Enter a number from -2147483648 (0x80000000) to 2147483647 (0x7FFFFFFF).
Enter a number from 0 (0x0) to 4294967295 (0xFFFFFFFF).
Enter a number like -123.456e-10 (needs work).
Enter a number like -123.456e-99 (needs work).
Enter the segment selector as a 4-digit hex value.
Enter the segment offset as a 4-digit hex value.
Enter byte data and then press Enter or Esc.
Enter ASCII data and then press Enter or Esc.
            Flags Register
Zero flag:%1       (1 if zero result)
Carry flag:%2      (1 if 2**16 carry)
Sign flag:%3       (1 if sign bit on)
Overflow flag:%4   (1 if signed over)
Direction flag:%5  (1 if dec si/di)
Parity flag:%6     (1 if even parity)
Auxiliary carry:%7 (1 if 2**4 carry)
  Edit Registers

 Esc,
    Exit regs
--,--
|   Move cursor
   Move cursor
 0..9,a..f   Change reg.



  General Help

SD386 is a source-level debugger for OS/2.  It debugs programs
compiled with IBM C Set/2, Microsoft C, or PL/X-86.  SD386
debugs 32-bit, 16-bit, and mixed 16- and 32-bit applications.
SD386 has full keyboard and mouse support.  It has a full set of
accelerator keys.  It has an action bar with these pull-downs:
 File
  File functions, browse, restart, & quit.
 Run
  Execute the target application in various ways.
 Breakpoints
  Set/clear various kinds of breakpoints.
 Search
  Text string search functions.
 Data
  Watch, show, expand, and edit data items.
 View
  SD386 window selection.
 Settings
  Colors, exceptions, assembler settings.
 Misc
  Call stack, thread, DLL, and register info.
 Help
  Display general and keyboard help information.
You can use the mouse or keyboard to select a line in the source
window.  Click the right mouse button on a line to bring up a
menu of functions available for that line.  Generally, you can
use the mouse anywhere you can use the keyboard.  Use the up and
down arrows on the action bar to change the size of the data
window.


  AL/86 Mnemonics

Sets the disassembly to use AL/86 mnemonics.  These mnemonics
coordinate with PL/X-86 assembly listings.


  Intel Mnemonics

Sets the disassembly to use Intel mnemonics.


  Data Window

The data window allows you to watch simple and complex variables
and view storage. You can expand complex variables into their
component parts.  You can use simple C-like expressions as
formulas to be watched.  You can changed the display format for
any item.
Think of the data window as a slate upon which you can put
variable and formula names.  In that slate, you can scroll up
and down, move to the beginning or end, or move by window.  You
can also expand or shrink the size of the window.  You can hide
the data window and redisplay it.
You can edit the formulas and the displayed storage.  Use the
mouse and/or the keyboard to move to the area you wish to edit.
Press Enter when you've finished.


  Assembler Window

The assembler window shows you mixed source and disassembly or
disassembly only.  In this view, you can choose Intel or AL/86
mnemonics.  When you single step in this view, you are stepping
one disassembled instruction at a time instead of one source
line at a time.  This allows you to see what is going on at the
machine level.
Each disassembled instruction contains the address of the
instruction, the hex bytes, the disassembled instruction (in
either mnemonic format), the operand(s), and the value of the
storage of the operand(s) if applicable.
You may wish to view or edit the contents of the registers while
in the assembler window.  The Registers (S_F10) and Edit
Registers items are in the Misc pulldown on the action bar.


  Action Bar

Activates the action bar at the top of the SD386 screen.


  Keys Help

Data type is UNSIGNED CHAR (8 bits).
Data type is UNSIGNED SHORT (16 bits).
Data type is UNSIGNED LONG (32 bits).
Data type is LONG DOUBLE (80 bits).
Do you want to exit ESP? Enter Y or N.
Go to a specific source file line number.
What action do you want to take?
 1. Stop the debuggee.
 2. Exit SD386.


  Processes

Mouse Input
Key Input
 Action

 Highlight a process
<Enter>
Enter
 Give focus to the highlighted process
<Cancel>
Esc
 Exit without any action
<Help>
F1
 See this Help panel


  MSHGET Help



  MSHPUT Help

Saves the current set of breakpoints in a file.  By default,
breakpoints are stored in the current directory with a name based
on the EXE that you're debugging.  For example, if you're
debugging MYPGM.EXE, then the breakpoint file will be named
MYPGM.BRK.  To save the breakpoints in a specific file and
directory, you can specify an SD386BRK environment variable as
follows:
Set SD386BRK=d:\mybrks\mybrks.brk
Restores a set of breakpoints from a a file.  By default,
breakpoints are stored in the current directory with a name based
on the EXE that you're debugging.  For example, if you're
debugging MYPGM.EXE, then the breakpoint file will be named
MYPGM.BRK.  To restore breakpoints from a specific file and
directory, you can specify an SD386BRK environment variable as
follows:
Set SD386BRK=d:\mybrks\mybrks.brk
You can edit a breakpoint file using an editor.  You can also
start an editor session from within a debug session by defining
an SD386EDITOR environment variable.
 Set SD386EDITOR=e
You do not have to include a .exe extension.  You can if you like, but
SD386 will add it for you if it isn't there.  You can also include an
explicit path if you want, but if you don't, SD386 will look along the
PATH environment variable that it inherited from the session the debugger
was started in.
SD386 will start your editor as a child session of the debugger and the
editor session will be terminated when you quit the debugger.  Some
editors may not terminate when the debugger quits.  In this case, the
editor refused to die when OS/2 sent a kill process signal to the
editor process.  Both EPM and the System Editor will terminate when you
quit the debugger.
After you have edited and saved a breakpoint file, SD386 will
update the breakpoints the next time you execute any of the go or
step commands under the Run pulldown.  You do not have to end the
edit session before the breakpoints will be updated.  But, you do
have to save the file.
When you're debugging PM apps and not using a remote connection to a
target machine, then you'll need to use a fullscreen or window
compatible editor.  Else, you'll probably hang the machine.  SD386 will
force the editor into a fullscreen session.  If you inadvertently use a
PM editor, then you will get a message and SD386 will not start the
editor session.
   { dll/exe, -----function name-------------------------------------- }
               |                            |   |      |  |         |
               |                            |    --,D--    --,COND--
                ---filename--,--line number-
   where:
      dll/exe       = The name of the executable where you want to set the
                      breakpoint.  Path information will be ignored since the
                      path is defined by the LIBPATH environment in
                      config.sys.  The .EXE or .DLL extension is optional.
      function name = Function name where you want to set the breakpoint.
      filename      = The file name of the source file where you want to
                      set the breakpoint.  Path information will be ignored
                      since it's not used to define the breapoint.  The
                      filename MUST contain an extension, for example,
                      myapp.c.
      line number   = Line number within filename where you want to set the
                      breakpoint.
      D             = Optional parameter to specify whether or not the
                      breakpoint is deferred(D).  It is not actually used
                      except for information.  When SD386 restores a
                      breakpoint file, it checks to see if the dll/exe has
                      been loaded, and if it hasn't, then the breakpoint is
                      deferred.
      COND          = Optional breakpoint condition.
HSaving breakpoints to
HRestoring breakpoints from
HUnknown function name. Enter "Yes" to defer. It
will be hit in all dlls containing this name.To restrict
it to a specific dll use Breakpoint->Set Deferred Break.
Sets a breakpoint on a function in a dynamically loaded dll.  Use
the syntax [dllname.]funcname.  If the dll name is not specified
then the breakpoint will be hit for all dlls containing the
function name.
Enter the name of the function optionally dot qualified with
a dll name.
Break when an address gets loaded.
Break when a dll gets loaded.
Enter the load address you want to break on.
Enter the dll name that you want to break on.
Displays a list of processes being debugged.
Turn on/off the display of member functions when showing classes.
Bad Invocation Option...%1
No EXE name.
Com Port Error.
Unable to open the modem file.
Execution Services Probe(ESP) not ready.
Cannot get your modem's attention. Check the following:
 - Modem power on.
 - Modem to computer cable connection. If you're using a homemade
   cable, be sure to connect the RTS/CTS signals.
 - Modem to telephone line connection.
 - Modem is connected to the correct com port.
If all of these are ok, then try resetting the modem by
turning the power off and back on.
The modem is not responding and a connect timeout has occurred.
Check the following:
 - Modem to telephone line connection.
User Profile Error.
Cannot read SD386.PRO.
Incorrect version of SD386.PRO.  The version number on the
first line of the file must match the version number of
SD386.EXE.
Keyword Start_Of_Defs not found in SD386.PRO.
Invalid Function specified in SD386.PRO.
 "%1" at Line No %2.
Invalid Attribute specified in SD386.PRO.
 "%1" at Line No %2.
Invalid Background Color in SD386.PRO.
 "%1" at Line No %2.
Invalid Foreground Color in SD386.PRO.
 "%1" at Line No %2.
Invalid Exception Type in SD386.PRO.
 "%1" at Line No %2.
Invalid Exception in SD386.PRO.
 "%1" at Line No %2.
Invalid Key in SD386.PRO.
 "%1" at Line No %2.
Nested comments not allowed in SD386.PRO.
 Line No %1 %2.
SD386.PRO Error.
Error reading file %1.
Cannot find %1.
DosStartSession is failing with rc=%1.
The following module is contributing to the failure:
DosDebug failure trying to initialize
%1 for debugging.
Unable to initialize %1.
Error trying to get the entry point for the following file:
Too many dlls.
The debug information for the following file is corrupt.
Can't build a source or assembler view.
Invalid com port number.
Unable to open the com port.
SD386 was able to open the com port but is unable to
set the com port parameters.
%1 references an undefined structure.
Unable  to register an exception handler.
Unable to start queue. System rc=%1.
The debugger has detected a "Resource Interlock" condition and
your application has been terminated. Debugging is stopped.
The response file associated with the /b invocation option is
either corrupt or cannot be found.  The response file must be in
the current directory or specified with an explicit path.
Unable to connect to esp...%1.
Netbios has an inadequate number of ...%1...  to start this
session or probe.  Check the PROTOCOL.INI in your IBMCOM
subdirectory and look for the allocation of the appropriate
resource.  You should see some entries that look like so:
   SESSIONS = 50
   NCBS = 95
   NAMES = 21
Bump the number of ...%1... and reboot your machine.
Netbios is unable to load ACSNETB.DLL.  Typically, you will
find this dll in a subdirectory similar to C:\IBMCOM\DLL after
you've installed LAPS.  Check for the installation of LAPS and
check your LIBPATH, then try again.
You have started SD386 in a VIO window.  The process you're
debugging is a PM app.  This combination will lead to a system
hang forcing you to reboot.  It is suggested that you end this
debug session and start the debugger in a full screen session.
If you prefer to run the debugger in a window, then you might
want to consider using a netbios or async remote connection.
If you choose to use full screen sessions running on a single
machine, then you might want to consider using the /x option to
turn off ctrl-esc and alt-esc access to the desktop.  If you
use this option and the debugger abnormally terminates leaving
ctrl-esc and alt-esc disabled, then simply enter SD386 /x to
turn it back on.
Error sending AT command to modem.
Error entering phone number.
DosDebug initializion is failing with rc=%1.
SD386 is unable to open the breakpoint file:
You need to define an SD386BRK environment variable that defines the
path and file name of the breakpoint file. For example:
Set SD386BRK=d:\mybrks\myapp.brk
Or, if you don't want to use an environment variable, then you can
default to SD386.BRK in the current directory.
Unmatched comment in breakpoint file:
 file name = %1
Breakpoint syntax error in:
check for a missing "{".
HBreakpoint error: missing dll or exe name. ( Esc to return.)
HBreakpoint error: missing function or (filename,line number). ( Esc to return.)
HBreakpoint error: missing line number.( Esc to return.)
HThe function name does not exist.( Esc to return.)
HThe file name is not linked for source level debug.( Esc to return.)
H%1 ( Esc to return.)
You need to define an SD386BRK environment variable
which includes the path and filename of the breakpoint
file. For example:
 Set SD386BRK=D:\MYBRKS\MYBRK.BRK
HError writing the breakpoint file.
You need to define an SD386EDITOR environment variable.
For example:
 Set SD386EDITOR=e
SD386 is unable to access the breakpoint file editor:
Check the definition of your SD386EDITOR environment variable and if
you haven't specified a path, then modify the PATH environment variable
to make the editor accessible. Or, add an explicit path to SD386EDITOR.
Unable to start the breakpoint file editor.
DosStartSession rc=%1
You are debugging a PM app and the editor you've chosen is also a
PM app.  You need to use a fullscreen or window compatible editor
to avoid hanging the system by going to the desktop.  If you use a
window compatible editor, then SD386 will start it in a full
screen session when debugging a PM app.
If you only want to browse the breakpoint file, then use the browser
provided with SD386 by selecting File->Browse File.
%1.dll is not currently loaded.
Try setting a deferred breakpoint.
%1 was not found in %2.
Invalid breakpoint definition.
Address %1 is not loaded.
DosLoadModule is failing with rc=%1. Check LIBPATH.
The following module is contributing to the failure:
DosQueryProcAddr is failing with rc=%1.
The following procedure is contributing to the failure:
Unable to access MSHLOOP.CMD. SD386 tries to access this file as
follows:
 1. Using the MSHHOME environment variable. For example, if
    MSHHOME=D:\MSH then SD386 will look in D:\MSH\BIN.
 2. By inferring it from where MSHCALC was loaded. If MSHCALC was
    loaded from D:\MSH\DLL then SD386 will look in D:\MSH\BIN.
Cannot start MSHLOOP.CMD.
DosStartSession is failing with rc=%1.
DosLoadModule/DosQueryProcAddr is failing with rc=%1.
Unable to load the dlls necessary to run TCP/IP...
 - SO32DLL.DLL
 - TCP32DLL.DLL
You should be able to find these in the \MPTN\DLL subdirectory
on the drive where OS/2 is installed. Check your TCP/IP installation
and your LIBPATH.
TCP/IP is not running.
TCP/IP error.
You need to specify a port number in your SERVICES file.
You should be able to find this file in the \MPTN\ETC subdirectory
on the drive where OS/2 is installed. The entry should look like:
 sd386     4321/tcp
where 4321 is the port number and tcp is the protocol.  You can
use whatever port number you wish as long as there is no conflict
with other well-known services.  Simply browse SERVICES and find
an available port number. Use lower case.
You need to specify a host name in your HOSTS file.  You should be
able to find this file in the \MPTN\ETC subdirectory on the drive
where OS/2 is installed.  The entry should look like:
9.51.136.80  clements.cv.lexington.ibm.com  elvis
where elvis is the alias for the foreign address specified by the
dotted decimal/name addresses.  Use whatever alias name you wish.
You need to start esp with the /t option.
If esp is started, then verify that the port numbers for SD386 in
the \MPTN\ETC\SERVICES file for both local and remote machines are
the same.