Newsgroups: comp.sys.amiga.programmer
Path: utzoo!utgpu!watserv1!sunee!avadekar
From: avadekar@sunee.waterloo.edu (Ashok Vadekar)
Subject: Lattice sscanf causes enforcer hit?
Message-ID: <1991Jun7.141715.16551@sunee.waterloo.edu>
Keywords: Lattice sscanf enforcer
Organization: University of Waterloo
Distribution: na
Date: Fri, 7 Jun 1991 14:17:15 GMT
Lines: 28

I think I have found a bug in Lattice's (5.10a) implementation of sscanf
(probably in scanf and fscanf as well).  The %*s formatting sequence seems
to generate enforcer hits: specifically a long read from address 0 followed
by a byte write to adress 0.  Could people with an '030 machine (ie with
an MMU) test the following two programs and reply to the net?


main() {
char string1[50],string2[50];

sscanf("  first_string    second_string   third_string ","%*s %s %s",
string1,string2);
}



main() {
char string1[50],string2[50];

sscanf("  first_string    second_string   third_string ","%s %s %s",
string1,string1,string2);
}

The second should run correctly, the first shold too, but seems to generate
the enforcer hits mentioned.

Ashok Vadekar