In an old thread Steven wrote -
>Eventually ICAT was developed. At first it only understood CodeView and
>Visualage C debug formats. This was because the OS/2 version of
>Microsoft C was used to develop many of the .ADD and .SYS device drivers.
>CSet/2 and its successor VAC were used to develop VDD's.
>More recently, .sym file support was added to ICAT.
>The most efficient way to use ICAT is to place copies of your binaries and
>the .sym files on the host and tell ICAT where they are. ICAT can get the
>debug data from the MUT but it's a lot slower.
Unfortunately I can't get ICAT to work with my example file (part of a bigger project)
with debugging information.
I tried wlink with OP SYMFILE. The symfile is about 60k. When I start the application on
the MUT with this sym file it does not run. One of the first statements in main() is
printf. The printf statement seems to be not reached when running under ICAT with the
watcom sym file.
Next I created a symfile with Stevens mapsymw.pl
script out of the map file. This sym file
is only 15k. Now my exe runs and shows the printf messages. But as before when I break
with ICAT I do not see any symbolic information.
My ICAT is Version 4.06.00 which is the latest which I collected over the years. It's from
about 2002. Is there a newer version somewhere?
Anyone successfully run remote source level debugging with ICAT and wcc386 and wlink?
Some time ago I tried to convince watcom to produce CodeView debugging information. But I
didn't get working source level debugging with ICAT too.
Any hints to get ICAT source level debugging with watcom are welcome.