cliff@.UCalgary.CA (09/29/89)
Hello all,
I couple of things :
(a)
I see to have an RS2030 with an internal 172 Mb disc that needs re-formatting.
Background :
On attempting to "cat" a couple specific text files on this disc, I will
get text interleaved with messages of the form :
SCSI 1L0: physical block address 0xA989 (43401)
SCSI 1L0: error code 0x11 (17): unrecovered read error in DATA field
...with the loss of text "blocks" at these points.
The RISC/os 4.00 release notes gives procedures for the SMD and ESDI drives
on the M/500, 800, 1000, and 2000 systems (sigh) and the RISC/os 4.10 release
notes don' give any procedures.... could some kind netter with the RS2030
doc. set please send me the details on re-formatting a 172Mb (cdc 94351)
disc drive?
(b)
"dbx" in a "bsd43" environment seems to have problems...(?). I have a
program that I wish to debug usng "dbx". If I compile it via :
% cc -systype bsd43 -g <prog>.c
and enter dbx, dbx is convinced that the "source is unavailable" and that
the file has either been stripped or not compiled with "-g". BUT, I have
a statement in the program of the form :
if (FUNCTION(<circa a dozen parameters>) == NULL) {
< report error >
}
and if I comment this baby out, I'm able to use "dbx" without any problem.
Further, I've encountered this same problem in another program, and this
one functions just fine! Same, behavour in "dbx", and once I track it down,
there is some snippet of perfectly legal C-code that if I comment it out,
"dbx" works fine....
Anyone else encounter this?
Cliff
--
Cliff Marcellus UUCP : {any backbone}!calgary!ssg-vax-a!cliff
Institute for Space Research DOMAIN : cliff@ssg-vax-a.phys.UCalgary.CA
Dept of Physics and Astronomy SPAN : CANCAL::CLIFF
The University of Calgary "If it's not fun, don't do it!"