Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: nospam_2019@efbe.prima.de
Newsgroups: comp.os.os2.programmer.misc
Subject: Re: Does ICAT understand watcom .sym files?
Date: Sun, 29 Dec 2019 17:39:43 +0100
Lines: 26
Message-ID: <h6s36fFeg45U1@mid.individual.net>
References: <qu7noc$q7k$1@dont-email.me>
Reply-To: fbeythien@gmx.de
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Trace: individual.net VhJJVqCPP2xEbUTIDvx9wwdT35xkLvwE5WAgAZeV2pgDj2XNs=
Cancel-Lock: sha1:O5p1H2j5gtdaxB2P1Wig1sb2mv8=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
In-Reply-To: <qu7noc$q7k$1@dont-email.me>
Content-Language: de-DE
Xref: csiph.com comp.os.os2.programmer.misc:1667

Am 28.12.19 um 15:10 schrieb Andi B.:
> 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.
>>

...

> 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.
> 
> Regards, Andreas

Hello Andi,

What prevents using OW remote debugging?
CU/2
Frank