From marksalzwedel at yahoo.com Wed Dec 22 13:09:46 2004 From: marksalzwedel at yahoo.com (Mark Salzwedel) Date: Wed Mar 22 17:10:49 2006 Subject: [splint-discuss] errors dissappear when splinting subdirectories Message-ID: <20041222180946.40129.qmail@web20921.mail.yahoo.com> I'm using Splint to check code that is kept in a number of subdirectories. Up until now, I've just copied all of the files into a common directory and run Splint from there and everything works fine. Now I'd like to get it to run properly so I don't have to copy/paste the files from their proper subdirectories. I've created a batch file like so: splint (a bunch of flags) ..\asm\*.h ..\config\*.c ..\config\*.h (etc.) It seems to sort of work, except that I get no errors when running this way (except for the lines using /*@t1@*/, etc., which now complain that no errors were found.) Obviously it is reading the files, or else I wouldn't get these warnings about not finding expected errors. Any idea what's up? Thanks. - Mark From gerald at ethereal.com Tue Dec 28 18:05:06 2004 From: gerald at ethereal.com (Gerald Combs) Date: Wed Mar 22 17:10:49 2006 Subject: [splint-discuss] PRIu64 parse error Message-ID: <41D1E6A2.7030403@ethereal.com> When trying to run the following through splint: #include [ ... ] if (cap_file_size) printf("File Size: %" PRIu64 " bytes\n", cf_info->filesize); the following error pops up: Splint 3.1.1 --- 19 Jul 2004 capinfos.c:109:50: Parse Error. (For help on parse errors, see splint -help parseerrors.) Is there any way to get this to work? A quick search of the archives turns up a couple of matches for this problem, but no solutions. From Ralf.Wildenhues at gmx.de Wed Dec 29 03:15:43 2004 From: Ralf.Wildenhues at gmx.de (Ralf Wildenhues) Date: Wed Mar 22 17:10:49 2006 Subject: [splint-discuss] PRIu64 parse error In-Reply-To: <41D1E6A2.7030403@ethereal.com> References: <41D1E6A2.7030403@ethereal.com> Message-ID: <20041229081543.GA31012@iam.uni-bonn.de> * Gerald Combs wrote on Wed, Dec 29, 2004 at 12:05:06AM CET: > When trying to run the following through splint: > > > #include > > [ ... ] > > if (cap_file_size) printf("File Size: %" PRIu64 " bytes\n", > cf_info->filesize); splint does not (yet) support C99, esp. inttypes. I submitted a patch to support most of these at one time (don't remember though, whether PRI* was among them), but splint development seems to have come to a grinding halt unfortunately. Regards, Ralf From winged__wolf at hotmail.com Thu Dec 30 03:59:46 2004 From: winged__wolf at hotmail.com (Aerowolf) Date: Wed Mar 22 17:10:49 2006 Subject: [splint-discuss] PRIu64 parse error In-Reply-To: <20041229081543.GA31012@iam.uni-bonn.de> Message-ID: If splint development has come to a grinding halt, perhaps it's time to fork the project. (It's licensed under GPLv2, according to CVS, even though the splint 3.1.1 tarball doesn't actually have the GPL text within it.) Either that, or someone should email the admins of the splint project on sourceforge and ask for project administration rights, to take over the development. -Kyle Hamilton -----Original Message----- From: splint-discuss-bounces@cs.virginia.edu [mailto:splint-discuss-bounces@cs.virginia.edu] On Behalf Of Ralf Wildenhues Sent: Wednesday, December 29, 2004 1:16 AM To: splint-discuss@cs.virginia.edu Subject: Re: [splint-discuss] PRIu64 parse error * Gerald Combs wrote on Wed, Dec 29, 2004 at 12:05:06AM CET: > When trying to run the following through splint: > > > #include > > [ ... ] > > if (cap_file_size) printf("File Size: %" PRIu64 " bytes\n", > cf_info->filesize); splint does not (yet) support C99, esp. inttypes. I submitted a patch to support most of these at one time (don't remember though, whether PRI* was among them), but splint development seems to have come to a grinding halt unfortunately. Regards, Ralf _______________________________________________ splint-discuss mailing list splint-discuss@cs.virginia.edu http://www.splint.org/mailman/listinfo/splint-discuss From kost at imn.htwk-leipzig.de Thu Dec 30 07:32:49 2004 From: kost at imn.htwk-leipzig.de (Stefan Kost) Date: Wed Mar 22 17:10:50 2006 Subject: [splint-discuss] PRIu64 parse error In-Reply-To: References: Message-ID: <41D3F571.5090908@imn.htwk-leipzig.de> hi hi, +1 from me to. a new release would be great. Especially as there seem to be useful patches out there. When I build the valinnal splint 3.1.1 it fails to e.g. parse glib-header (due to VARARG macros). When doing the same on my gentoo box it works. Seems that that install a patched version. Stefan Aerowolf wrote: > If splint development has come to a grinding halt, perhaps it's time to fork > the project. (It's licensed under GPLv2, according to CVS, even though the > splint 3.1.1 tarball doesn't actually have the GPL text within it.) > > Either that, or someone should email the admins of the splint project on > sourceforge and ask for project administration rights, to take over the > development. > > -Kyle Hamilton > > -----Original Message----- > From: splint-discuss-bounces@cs.virginia.edu > [mailto:splint-discuss-bounces@cs.virginia.edu] On Behalf Of Ralf Wildenhues > Sent: Wednesday, December 29, 2004 1:16 AM > To: splint-discuss@cs.virginia.edu > Subject: Re: [splint-discuss] PRIu64 parse error > > * Gerald Combs wrote on Wed, Dec 29, 2004 at 12:05:06AM CET: > >>When trying to run the following through splint: >> >> >>#include >> >> [ ... ] >> >> if (cap_file_size) printf("File Size: %" PRIu64 " bytes\n", >> cf_info->filesize); > > > splint does not (yet) support C99, esp. inttypes. I submitted a patch to > support most of these at one time (don't remember though, whether > PRI* was among them), but splint development seems to have come to a > grinding halt unfortunately. > > Regards, > Ralf > _______________________________________________ > splint-discuss mailing list > splint-discuss@cs.virginia.edu > http://www.splint.org/mailman/listinfo/splint-discuss > _______________________________________________ > splint-discuss mailing list > splint-discuss@cs.virginia.edu > http://www.splint.org/mailman/listinfo/splint-discuss > -- \|/ Stefan Kost <@ @> private business +-oOO-(_)-OOo------------------------------------------------------ - - - - - | __ Address Simildenstr. 5 HTWK Leipzig, Fb IMN, Postfach 301166 | /// 04277 Leipzig 04251 Leipzig | __ /// Germany Germany | \\\/// Phone +49341 2253538 +49341 30766101 | \__/ EMail st_kost_at_gmx.net kost_at_imn.htwk-leipzig.de | WWW www.sonicpulse.de www.imn.htwk-leipzig.de/~kost/about.html ===-=-=--=---=---------------------------------- - - - - - -------------- next part -------------- A non-text attachment was scrubbed... Name: kost.vcf Type: text/x-vcard Size: 345 bytes Desc: not available Url : http://www.cs.Virginia.EDU/pipermail/splint-discuss/attachments/20041230/ad0b0651/kost.vcf From Ralf.Wildenhues at gmx.de Thu Dec 30 07:49:26 2004 From: Ralf.Wildenhues at gmx.de (Ralf Wildenhues) Date: Wed Mar 22 17:10:50 2006 Subject: [splint-discuss] PRIu64 parse error In-Reply-To: <41D3F571.5090908@imn.htwk-leipzig.de> References: <41D3F571.5090908@imn.htwk-leipzig.de> Message-ID: <20041230124926.GA30421@iam.uni-bonn.de> Please don't top-post nor fullquote -- thank you. * Stefan Kost wrote on Thu, Dec 30, 2004 at 01:32:49PM CET: > Aerowolf wrote: > > If splint development has come to a grinding halt, perhaps it's time to fork > > the project. (It's licensed under GPLv2, according to CVS, even though the > > splint 3.1.1 tarball doesn't actually have the GPL text within it.) > > > > Either that, or someone should email the admins of the splint project on > > sourceforge and ask for project administration rights, to take over the > > development. IIRC the author has offered this before but nobody has stepped up to maintain it. > +1 from me to. > a new release would be great. Especially as there seem to be useful patches out > there. Find somebody with time and skills to do it. I'd be glad to send in patches eventually but I don't have the spare resources for (useful) maintenance. Regards, Ralf