duane@anasaz.UUCP (Duane Morse) (03/11/90)
lint1 seems to have a fixed limit on the number of structure definitions it can handle, and the number isn't very big. The lint shell script points out the line at which it failed but attributes the problem to cpp; it's really lint1. A very odd bug I've encountered has to do with a System V semaphore. If created by a program owned by root and with user setuid set, it can only be deleted by that program or by someone with "root" privileges, even if the semaphore has -ra-ra-ra protection. In our instance, the group was NOT root, but group privileges didn't seem to play any role. Our machine is an MIS-5/02. -- Duane Morse e-mail: duane@anasaz (or ... asuvax!anasaz!duane) (602) 861-7609
tim@brspyr1.BRS.Com (Tim Northrup) (03/15/90)
duane@anasaz.UUCP (Duane Morse) writes: >lint1 seems to have a fixed limit on the number of structure definitions >it can handle, and the number isn't very big. The lint shell script >points out the line at which it failed but attributes the problem to cpp; >it's really lint1. Yeah, we hit this one too. It appears that the 'ucb' lint it not so limited (either it doesn't have one, or we just haven't hit it yet). We just do all our linting using the ucb lint program when we run into that problem (it works, though the output is horrible compared to what the att lint provides). For what its worth ... -- Tim -- Tim Northrup +------------------------------------------+ +---------------------------------+ GEnie: T.Northrup | UUCP: uunet!crdgw1!brspyr1!tim | Air Warrior: "Duke" | ARPA: tim@brspyr1.BRS.Com +------------------------------------------+