Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ittatc!dcdwest!sdcsvax!ucbvax!daemon
From: daemon@ucbvax.BERKELEY.EDU (The devil himself)
Newsgroups: mod.computers.vax
Subject: Re: VMS C help needed
Message-ID: <8602101030.AA01305@ucbvax.berkeley.edu>
Date: Sun, 9-Feb-86 10:10:13 EST
Article-I.D.: ucbvax.8602101030.AA01305
Posted: Sun Feb  9 10:10:13 1986
Date-Received: Tue, 11-Feb-86 03:33:09 EST
References: <8602070150.AA10267@ucsf-cgl.ARPA>
Organization: The ARPA Internet
Lines: 20
Approved: info-vax@sri-kl.arpa

> I've been converting a program to run under VMS C C2.0-003.  If I use
> the old library from VMS C V1.xxx (crtlib.olb), everything works fine.
> When I use the new library (vaxcrtl.olb, creation date 27-APR-1985),
> sscanf() seems to fail at random intervals; that is, sscanf() claims
> there are no matches (returns -1) even though the input string is
> "1 molecules\n" and the format string is "%d molecules".  Has anyone
> else seen anything similar?
> 
> Things get *real* interesting when I compile and link my program with
> the debug option.  If I "go" without setting any watch/break points,
> it fails.  If I set a watch point, it sometimes does not fail.  If I
> set a break point and look at values, it *never* fails.  I either need
> a VMS C guru or a psychiatrist.
> 
> *Any* help would be greatly appreciated.  Thanks,
> 
> 					Conrad Huang

Watch out for shared images;  you probably have a shareable version of
the old library installed.