Groups | Search | Server Info | Login | Register

Groups > comp.os.os2.programmer.misc > #1675

Re: Does ICAT understand watcom .sym files?

Show all headers | View raw

Hi Andy,

after fuzzing around with Watcom a little I think I now know how to set 
up the MUT and the host:

MUT (assuming its internet address is 192.168.178.220):
tcpserv -tr=tcp;192.168.178.220 3563
(this will start the server on the MUT that expects to receive debugging 
calls, it will listen to port 3563 )

HOST (machine where WDW executes):
wdw /tr=tcp;192.168.178.220:3563 @Rc:\os2\boot\mydriver.sys
(the latter will try to access the driver binary on the MUT (@R) in 
directory c:\os2\boot\mydriver.sys, mydriver.sys needs to contain native 
WATCOM debug info, I suppose)


You can freely choose the port number. Adjust the IP address (of the 
MUT) to match your setup.

Let us know if that works for you. Obviously, you need to have WATCOM 
installed on both, host and MUT.


Lars


On 30.12.19 14.15, Andi B. wrote:
> nospam_2019@efbe.prima.de schrieb:
>> 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
>>
>
> Hi Frank,
> nice to see you still hanging around here :-)
>
> wdw.exe - beside the ugly fonts it uses you mean?
>
> Starting "wdw /tr=net ..." shows a message 'DosSMRegisterDD not allowed'
> (or similar). The same with wd.exe.
>
> I try to debug gareport.exe. This is a CLI app which tries to detect the
> installed graphic card and it's capabilities via SNAP. Although the app
> runs fine without PM I couldn't manage to debug it with OW. But it runs
> under ICAT control.
>
> Greetings, Andi

Back to comp.os.os2.programmer.misc | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Does ICAT understand watcom .sym files? "Andi B." <andi.b@gmx.net> - 2019-12-28 15:10 +0100
  Re: Does ICAT understand watcom .sym files? nospam_2019@efbe.prima.de - 2019-12-29 17:39 +0100
    Re: Does ICAT understand watcom .sym files? Lars Erdmann <lars.erdmann@arcor.de> - 2019-12-30 09:00 +0100
      Re: Does ICAT understand watcom .sym files? Marcel Mueller <news.5.maazl@spamgourmet.org> - 2019-12-30 11:30 +0100
        Re: Does ICAT understand watcom .sym files? "Andi B." <andi.b@gmx.net> - 2019-12-30 14:34 +0100
        Re: Does ICAT understand watcom .sym files? Lars Erdmann <lars.erdmann@arcor.de> - 2019-12-30 17:24 +0100
      Re: Does ICAT understand watcom .sym files? "Andi B." <andi.b@gmx.net> - 2019-12-30 14:17 +0100
    Re: Does ICAT understand watcom .sym files? "Andi B." <andi.b@gmx.net> - 2019-12-30 14:15 +0100
      Re: Does ICAT understand watcom .sym files? Lars Erdmann <lars.erdmann@arcor.de> - 2019-12-30 17:20 +0100
        Re: Does ICAT understand watcom .sym files? "Andi B." <andi.b@gmx.net> - 2019-12-31 13:16 +0100
      Re: Does ICAT understand watcom .sym files? Dave Yeo <dave.r.yeo@gmail.com> - 2019-12-30 13:03 -0800
        Re: Does ICAT understand watcom .sym files? "Andi B." <andi.b@gmx.net> - 2019-12-31 12:57 +0100
          Re: Does ICAT understand watcom .sym files? Dave Yeo <dave.r.yeo@gmail.com> - 2019-12-31 12:10 -0800
  Re: Does ICAT understand watcom .sym files? Lars Erdmann <lars.erdmann@arcor.de> - 2019-12-30 09:14 +0100
    Re: Does ICAT understand watcom .sym files? "Andi B." <andi.b@gmx.net> - 2019-12-30 14:47 +0100

csiph-web