home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
icat.zip
/
icatos2.zip
/
icatos2
/
readme.txt
Wrap
Text File
|
2000-11-28
|
5KB
|
138 lines
README.TXT
----------
See ICAT home page for more details - http://service.boulder.ibm.com/icat
.SYM FILE PROCESSING
ICAT now enables you to view limited symbol information in the Disassembly
view of an executable file compiled with no debug information if a separate
symbol file is supplied. Using the link symbol information from a separate
(*.sym) file, function names are annotated to the disassembly lines for
function calls and function entry points making it easier for you to navigate
through disassembly code.
To enable viewing of the symbol information in Disassembly view, set up the
host and target machines. Then place a copy of the symbol (*.sym) file in the
same subdirectory pointed to by the CAT_HOST_BIN_PATH environment variable on
the host.
Whether the executable is located on the target machine or is on both the host
and target machines, there is no difference in performance. Currently, the
symbol file must be located on the host machine.
If the executable to be debugged was compiled to enable a separate map file to
be generated, then the symbol file is obtained by running the MapSym.exe
utility on that map (*.map) file. Make certain that the symbol file has the
same name as the executable.
UDP COMMUNICATIONS
In order to connect to the target machine via UDP, the following two
environment variables on the host machine must be modified from their settings
for serial communications:
set CAT_MACHINE=x.x.x.x:nnnn
set CAT_COMMUNICATION_TYPE=UDP
where x.x.x.x is the IP address of the target machine, and
nnnn is the KDB port number.
The value of 1000 is suggested for the KDB port number.
Also, KDBNET.SYS must be installed on the target system, as per the following
steps:
1) In CONFIG.SYS, locate the line containing PROTMAN.OS2
2) After this line, enter:
DEVICE=x:\y\KDBNET.SYS /V /Id.d.d.d /Ppppp
where x and y are the drive letter and path to the directory where you
wish to store KDBNET.SYS. The IBMCOM subdirectory is probably the
most convenient place to put it.
d.d.d.d is the IP address of the target machine
pppp is the port number on which KDBNET will accept UDP data
(1000 is the recommended port number)
3) Locate the PROTOCOL.INI file, which should be in the IBMCOM subdirectory.
4) In the stanza that begins with [IBMLXCFG], add the following line:
kdbnet_nif = kdbnet.nif
5) Add a new stanza to PROTOCOL.INI:
[KDBNET_nif]
Bindings = IBMFEEO2_nif
DriverName = KDBNET$
KDBIPADDR = "d.d.d.d"
KDBSNETMASK = "255.255.248.0"
KDBPORT = 1000
NMPORT = 1001
BCASTNOTIFY = "YES"
NNOACTION = "C"
where d.d.d.d is replaced with the IP address of the machine.
6) Look at the other stanzas of the PROTOCOL.INI file. If the value of
"Bindings =" is something other than IBMFEE02_nif, use that value instead
of IBMFEE02_nif.
7) Copy the file KDBNET.NIF to the IBMCOM\PROTOCOL subdirectory.
8) Reboot the target machine. If KDBNET is properly installed, you should see
a "banner" during the bootup process.
NOTE! Don't reboot the target machine from ICAT's File pulldown if KDBNET.SYS
is installed on that target. ICAT and KDB and KDBNET.SYS can't resync in this
manner.
Note! limitations using KDBNET.SYS/ICAT UDP debugging:
On the target machine, KBDNET.SYS does not function until the RUN=NETBIND.EXE
has been completed. This occurs AFTER all device drivers have been loaded and
initialized, therefore ICAT thru KBDNET.SYS cannot be used to debug device
driver loading or initialization.
The CONFIG.SYS contains a RUN=\IBMCOM\PROTOCOL\NETBIND.EXE statement. After
NETBIND.EXE is run, UDP packets will be available for KDBNET.SYS to examine.
Therefore, the earliest one can use ICAT in UDP mode is after NETBIND.EXE has
completed. To debug a device driver during system initialization time, one
must use ICAT in serial mode.
HELP AND MESSAGE FILE NOTE
Special note! If you have a country code page that is described by the
following matrix, ICAT will look for its help and message files accordingly:
Japan GAM5HELJ.HLP GAM5LDEJ.MSG
Taiwan GAM5H088.HLP GAM5L088.MSG
France GAM5H033.HLP GAM5L033.MSG
Germany GAM5H049.HLP GAM5L049.MSG
China GAM5H086.HLP GAM5L086.MSG
In these instances, you can rename GAM5HELP.HLP to GAM5HELJ.HLP and GAM5LDE.MSG
to GAM5LDEJ.MSG (in the case of a Japan country code page). ICAT looks for
these files because it is possible that in the future, IBM will provide
translated modules for these countries.