[comp.unix.i386] Codeview under SCO UNIX

capitain.pad@nixpbe.uucp (Pit Capitain) (05/02/90)

walter@mecky.UUCP (Walter Mecky) writes:

>After compiling with the -g option and starting codeview under SCO UNIX,
>"cv" reports:
>	cvtcoff: fatal error - expected aux record after .text 16

>and continues in assembler mode. In the dialog window it writes 
>"no symbol information" and refuses to switch to C-source mode ==>
>"unable to open file".

>Anybody out there who can help ?

You have to use the "-xenix" option together with the "-g" option,
if you compile with Microsoft's "cc".
AT&T's "rcc" compiler only needs the "-g" option.
--
Pit Capitain, Nixdorf Computer AG, Dept. PXD-S2

Usenet: capitain.pad@nixbur.uucp, capitain.pad@nixntc.uucp
Eunet:  capitain.pad@nixpbe.uucp
X.400:  S=capitain;O=pad;P=nixdorf;A=dbp;C=de  (capitain@pad.nixdorf.dbp.de)

seanf@sco.COM (Sean Fagan) (05/04/90)

In article <1673@nixpbe.UUCP> capitain.pad@nixpbe.uucp (Pit Capitain) writes:
>walter@mecky.UUCP (Walter Mecky) writes:
>>After compiling with the -g option and starting codeview under SCO UNIX,
>>"cv" reports:
>>	cvtcoff: fatal error - expected aux record after .text 16
>You have to use the "-xenix" option together with the "-g" option,
>if you compile with Microsoft's "cc".
>AT&T's "rcc" compiler only needs the "-g" option.

This is now fixed, due to improvements in both the cvtomf and cvtcoff
utilities.  SCO Support has a disk with the new utilities, and a couple of
other things, I believe.  I'm not sure what it's called (perhaps someone who
has gotten it could post the information?), but support should know about
it.

-- 
-----------------+
Sean Eric Fagan  | "It's a pity the universe doesn't use [a] segmented 
seanf@sco.COM    |  architecture with a protected mode."
uunet!sco!seanf  |         -- Rich Cook, _Wizard's Bane_
(408) 458-1422   | Any opinions expressed are my own, not my employers'.