Groups | Search | Server Info | Login | Register

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

Re: Does ICAT understand watcom .sym files?

Show key headers only | View raw

Lars Erdmann schrieb:
> Have you placed the sym file into the same directoy on the HOST (where ICAT executes) as
> the driver binary ? And have you modified the ICAT cmd file to point to that directory ?
>
> Yes, I seem to remember that with the approach above, I had limited debugging capability
> (with the wat2map.cmd and mapsym.exe approach).

Yes I see this now too. Very limited but at least I see symbols for the functions I use. I 
hadn't any clue what 'symbolic/symdeb' debugging means before. I'm used to source level 
debugging since > 30 years. I didn't realize that that limited symbol info is all what I 
can expect from ICAT running with .sym files.

>
> Needless to say that sym file support is very restricted. It only knows public symbol
> names, it has no clue of type definitions and no clue of stack variables.
> That also means that you should NOT mark any variables or routines as "static" if you want
> to see their symbol names. "static" will prevent that symbol name from showing up in the
> map file and consequently it will also be missing from the symbol file (check your map file).
>

Not needless for me. I didn't think about that stuff well enough before. Thanks for 
clarification.

Andreas

>
> What I have done in the past is write code that compiles with cl.exe (+ some assembler
> code) or icc.exe (VAC) and compile+link with Codeview / HLL debug info. That'll allow to
> do full source code debugging over ICAT.
> Then, when everything works, you can switch over to Watcom.
>
>
> Lars
>
>
>
>
> On 28.12.19 15.10, Andi B. wrote:
>> 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.
>>
>> Regards, Andreas
>

Back to comp.os.os2.programmer.misc | Previous | Next — Previous 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