Xref: utzoo comp.unix.sysv386:8003 comp.lang.c:39210 comp.unix.programmer:1804
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!netcomsv!dsmythe
From: dsmythe@netcom.COM (Dave Smythe)
Newsgroups: comp.unix.sysv386,comp.lang.c,comp.unix.programmer
Subject: Re: SDB broken on SCO UNIX 3.2 ?
Keywords: sdb, cc -g , debugger, codeview
Message-ID: <1991May11.223919.15687@netcom.COM>
Date: 11 May 91 22:39:19 GMT
References: <1991May07.070123.12721@logixwi.uucp>
Sender: netnews@netcom.COM (USENET Administration)
Organization: Netcom - Online Communication Services  UNIX System {408 241-9760 guest}
Lines: 26

Regarding bugs in CodeView and SDB, There is a bug in cvtomf (run automatically
by cc, not rcc) that corrupts symbol tables.  It's been reported.  You'll see:
"No symbolic information" when cv or sdb comes up.  To reproduce it, try:

main()
{
  int x = -1;

  { { int a; } }
  { { int b; } }
  { { int c; } }
}

If you switch multiscreens while CodeView is loading (actually, while it is 
running cvtcoff to convert your COFF file to OMF for cv) cvtcoff will die,
and you'll get no symbolic information.  Just be patient :-)

If you are trying to use Codeview (perhaps sdb too?) on executables that
exist on NFS mounted directories, then it will occasionally refuse to
allow you to set breakpoints (I/O error (6?)).  I've even seen it accept
a breakpoint and not stop there!  *Sometimes* you can set a breakpoint
after you have started execution (g main; set bp; g).

Hope I can save somebody some grief...

D