From muneeswaranp at hcl.in Wed Mar 3 08:10:37 2010 From: muneeswaranp at hcl.in (Muneeswaran P-ERS,HCLTech) Date: Wed, 3 Mar 2010 18:40:37 +0530 Subject: [splint-discuss] Cgrammar, llgrammar, mtgrammar Message-ID: Hi, I am new to splint and going through the splint code ver3.1.1. I want to know the difference between Cgrammar.y, llgrammar.y, mtgrammar.y in splint. Why there are three grammar files available ? Regards, Munees. Tel: +91-44-42169999 Extn-2732 DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ----------------------------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.cs.virginia.edu/pipermail/splint-discuss/attachments/20100303/173b74d8/attachment.html From evans at cs.virginia.edu Wed Mar 3 09:13:30 2010 From: evans at cs.virginia.edu (David Evans) Date: Wed, 03 Mar 2010 09:13:30 -0500 Subject: [splint-discuss] Cgrammar, llgrammar, mtgrammar In-Reply-To: References: Message-ID: <4B8E6E8A.2070707@cs.virginia.edu> Hi Munees, All the .y files are bison grammars. The cgrammar.y is for parsing the C code, llgrammar.y is for parsing LCL specifications, and mtgrammar.y is for parsing mts files that define new annotations. --- Dave On 3/3/2010 8:10 AM, Muneeswaran P-ERS,HCLTech wrote: > Hi, > I am new to splint and going through the splint code ver3.1.1. > I want to know the difference between Cgrammar.y, llgrammar.y, > mtgrammar.y in splint. Why there are three grammar files available ? > Regards, > Munees. > Tel: +91-44-42169999 Extn-2732 > DISCLAIMER: > ----------------------------------------------------------------------------------------------------------------------- > > The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. > It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in > this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of > this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have > received this email in error please delete it and notify the sender immediately. Before opening any mail and > attachments please check them for viruses and defect. > > ----------------------------------------------------------------------------------------------------------------------- > > > _______________________________________________ > splint-discuss mailing list > splint-discuss at mail.cs.virginia.edu > http://www.cs.virginia.edu/mailman/listinfo/splint-discuss > From muneeswaranp at hcl.in Wed Mar 3 09:28:09 2010 From: muneeswaranp at hcl.in (Muneeswaran P-ERS,HCLTech) Date: Wed, 3 Mar 2010 19:58:09 +0530 Subject: [splint-discuss] Cgrammar, llgrammar, mtgrammar In-Reply-To: <4B8E6E8A.2070707@cs.virginia.edu> References: <4B8E6E8A.2070707@cs.virginia.edu> Message-ID: Hi Dave, Thanks for the input. One quick question: Is there any design doc/HTML/Ref available for source code implementation? So that I can read that first, before stealing others valuable time by asking simple questions ? Regards, Munees. Tel: +91-44-42169999 Extn-2732 -----Original Message----- From: splint-discuss-bounces at cs.virginia.edu [mailto:splint-discuss-bounces at cs.virginia.edu] On Behalf Of David Evans Sent: Wednesday, March 03, 2010 7:44 PM To: splint-discuss at mail.cs.virginia.edu Subject: Re: [splint-discuss] Cgrammar, llgrammar, mtgrammar Hi Munees, All the .y files are bison grammars. The cgrammar.y is for parsing the C code, llgrammar.y is for parsing LCL specifications, and mtgrammar.y is for parsing mts files that define new annotations. --- Dave On 3/3/2010 8:10 AM, Muneeswaran P-ERS,HCLTech wrote: > Hi, > I am new to splint and going through the splint code ver3.1.1. > I want to know the difference between Cgrammar.y, llgrammar.y, > mtgrammar.y in splint. Why there are three grammar files available ? > Regards, > Munees. > Tel: +91-44-42169999 Extn-2732 > DISCLAIMER: > ---------------------------------------------------------------------- > ------------------------------------------------- > > The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. > It shall not attach any liability on the originator or HCL or its > affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, > modification, distribution and / or publication of this message > without the prior written consent of the author of this e-mail is > strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. > > ---------------------------------------------------------------------- > ------------------------------------------------- > > > _______________________________________________ > splint-discuss mailing list > splint-discuss at mail.cs.virginia.edu > http://www.cs.virginia.edu/mailman/listinfo/splint-discuss > _______________________________________________ splint-discuss mailing list splint-discuss at mail.cs.virginia.edu http://www.cs.virginia.edu/mailman/listinfo/splint-discuss From evans at cs.virginia.edu Wed Mar 3 09:54:33 2010 From: evans at cs.virginia.edu (David Evans) Date: Wed, 03 Mar 2010 09:54:33 -0500 Subject: [splint-discuss] Cgrammar, llgrammar, mtgrammar In-Reply-To: References: <4B8E6E8A.2070707@cs.virginia.edu> Message-ID: <4B8E7829.4030903@cs.virginia.edu> Sorry, there's not real developer documentation other than the comments in the source code and the high-level descriptions in the research papers. --- Dave On 3/3/2010 9:28 AM, Muneeswaran P-ERS,HCLTech wrote: > Hi Dave, > > Thanks for the input. > > One quick question: Is there any design doc/HTML/Ref available for source code implementation? So that I can read that first, before stealing others valuable time by asking simple questions ? > > Regards, > Munees. > Tel: +91-44-42169999 Extn-2732 > From muneeswaranp at hcl.in Tue Mar 9 09:35:21 2010 From: muneeswaranp at hcl.in (Muneeswaran P-ERS,HCLTech) Date: Tue, 9 Mar 2010 20:05:21 +0530 Subject: [splint-discuss] Cgrammar.c: yypact[], yydefgoto[], yyr1[], yydefact[], yyr2[] In-Reply-To: <4B8E7829.4030903@cs.virginia.edu> References: <4B8E6E8A.2070707@cs.virginia.edu> <4B8E7829.4030903@cs.virginia.edu> Message-ID: Hi All, I am new to splint and going through the splint code ver3.1.1. I want some details on yypact[], yydefgoto[], yyr1[], yydefact[], yyr2[] in Cgrammar.c file. 1. As per my understanding, there are three stacks implemented for state, semantic values and location as yyssa[], yyvsa[] and yylsa[] respectively. But how these stack tables got linked to yypact[], yydefgoto[], yyr1[], yydefact[], yyr2[]. 2. Is it generated automatically from bison utility ? Is it done manually ? Please help me to understand this stuff. Regards, Munees. Tel: +91-44-42169999 Extn-2732 DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ----------------------------------------------------------------------------------------------------------------------- From muneeswaranp at hcl.in Tue Mar 9 09:35:21 2010 From: muneeswaranp at hcl.in (Muneeswaran P-ERS,HCLTech) Date: Tue, 9 Mar 2010 20:05:21 +0530 Subject: [splint-discuss] Cgrammar.c: yypact[], yydefgoto[], yyr1[], yydefact[], yyr2[] In-Reply-To: <4B8E7829.4030903@cs.virginia.edu> References: <4B8E6E8A.2070707@cs.virginia.edu> <4B8E7829.4030903@cs.virginia.edu> Message-ID: Hi All, I am new to splint and going through the splint code ver3.1.1. I want some details on yypact[], yydefgoto[], yyr1[], yydefact[], yyr2[] in Cgrammar.c file. 1. As per my understanding, there are three stacks implemented for state, semantic values and location as yyssa[], yyvsa[] and yylsa[] respectively. But how these stack tables got linked to yypact[], yydefgoto[], yyr1[], yydefact[], yyr2[]. 2. Is it generated automatically from bison utility ? Is it done manually ? Please help me to understand this stuff. Regards, Munees. Tel: +91-44-42169999 Extn-2732 DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ----------------------------------------------------------------------------------------------------------------------- From newlifewithg at gmail.com Mon Mar 15 03:12:29 2010 From: newlifewithg at gmail.com (A Z) Date: Mon, 15 Mar 2010 17:12:29 +0900 Subject: [splint-discuss] Newbie in Splint world Message-ID: <35b67cf61003150112j48761e1fx46469ed86cdceb4f@mail.gmail.com> Guys Just started to use splint in IDE of Visual C++ 2008 Expression Edition and its not working. When I execute splint it gives me the following log.Sorry for including this long log here. splint has not even touch the source code that I have written. Thanks in advance,AJ [ Command Line: Cannot open options file: C:\Program There was a problem reading an initialization file (Use -warnrc to inhibit warning) Command Line: Unrecognized file extension: Files\splint-3.1.1\bin\.splintrc (assuming .splintrc is C source code) warn when command line file does not have a recognized extension (Use -fileextensions to inhibit warning) Cannot open file: Files\splint-3.1.1\bin\.splintrc C:\include\vadefs.h(52,26): Datatype uintptr_t declared with inconsistent type: unsigned int A function, variable or constant is redefined with a different type. (Use -incondefs to inhibit warning) load file standard.lcd: Specification of uintptr_t: unsigned int * C:\include\crtdefs.h(490,26): Datatype size_t declared with inconsistent type: unsigned int load file standard.lcd: Specification of size_t: arbitrary unsigned integral type C:\include\crtdefs.h(506,26): Datatype intptr_t declared with inconsistent type: int load file standard.lcd: Specification of intptr_t: int * C:\include\crtdefs.h(524,26): Datatype ptrdiff_t declared with inconsistent type: int load file standard.lcd: Specification of ptrdiff_t: arbitrary integral type C:\include\crtdefs.h(530,24): Datatype wchar_t declared with inconsistent type: unsigned short int load file standard.lcd: Specification of wchar_t: arbitrary integral type C:\include\crtdefs.h(535,24): Datatype wint_t declared with inconsistent type: unsigned short int load file standard.lcd: Specification of wint_t: arbitrary integral type C:\include\crtdefs.h(536,24): Datatype wctype_t declared with inconsistent type: unsigned short int load file standard.lcd: Specification of wctype_t: arbitrary integral type C:\include\crtdefs.h(574,27): Parse Error: Suspect missing struct or union keyword: __int64 : long int. (For help on parse errors, see splint -help parseerrors.) *** Cannot continue. ] From Michael.Wojcik at microfocus.com Mon Mar 15 08:47:28 2010 From: Michael.Wojcik at microfocus.com (Michael Wojcik) Date: Mon, 15 Mar 2010 06:47:28 -0700 Subject: [splint-discuss] Newbie in Splint world In-Reply-To: <35b67cf61003150112j48761e1fx46469ed86cdceb4f@mail.gmail.com> References: <35b67cf61003150112j48761e1fx46469ed86cdceb4f@mail.gmail.com> Message-ID: <81F42F63D5BB344ABF294F8E80990C7902782425@MTV-EXCHANGE.microfocus.com> > From: splint-discuss-bounces at cs.virginia.edu [mailto:splint-discuss- > bounces at cs.virginia.edu] On Behalf Of A Z > Sent: Monday, 15 March, 2010 04:12 > > Guys > Just started to use splint in IDE of Visual C++ 2008 Expression > Edition and its not working. Using it under an IDE may not be the best plan. You'll have an easier time controlling the command line and environment running Splint from a console window. > When I execute splint it gives me the following log.Sorry for including > this long log here. > > [ > Command Line: Cannot open options file: C:\Program > There was a problem reading an initialization file (Use -warnrc to inhibit > warning) > Command Line: Unrecognized file extension: > Files\splint-3.1.1\bin\.splintrc (assuming .splintrc is C source code) > warn when command line file does not have a recognized extension (Use > -fileextensions to inhibit warning) You have spacey path names on the Splint command line, and they're not quoted. Here, the problem is a command line like: splint -f C:\Program Files\splint-3.1.1\bin\.splintrc Like all good programs, splint uses spaces as delimiters on its command line, so it reads that as "-f C:\Program", followed by another argument that's "Files\splint-3.1.1\bin\.splintrc". Arguments with spaces in the name need to be quoted: splint -f "c:\program files\splint-3.1.1\bin\.splintrc" Even better, do not use spacey paths, as they are a brain-dead convention introduced by Microsoft to make everyone's life harder. Install Splint in a sensible, spaceless path, and keep your sources in a similar one. > C:\include\vadefs.h(52,26): Datatype uintptr_t declared with > inconsistent type: > unsigned int > A function, variable or constant is redefined with a different type. > (Use > -incondefs to inhibit warning) > load file standard.lcd: Specification of uintptr_t: unsigned int * These other errors could be cascades from the failure to load your .splintrc, or they could be real problems with your source. There's no way for us to tell, since we cannot psychically see what in your source is producing them. -- Michael Wojcik Principal Software Systems Developer, Micro Focus From ok at cs.otago.ac.nz Mon Mar 15 17:54:01 2010 From: ok at cs.otago.ac.nz (Richard O'Keefe) Date: Tue, 16 Mar 2010 11:54:01 +1300 Subject: [splint-discuss] Newbie in Splint world In-Reply-To: <35b67cf61003150112j48761e1fx46469ed86cdceb4f@mail.gmail.com> References: <35b67cf61003150112j48761e1fx46469ed86cdceb4f@mail.gmail.com> Message-ID: <9724E77D-2F41-4A0D-A1C3-FFDF1F5238C3@cs.otago.ac.nz> On Mar 15, 2010, at 9:12 PM, A Z wrote: > Guys > Just started to use splint in IDE of Visual C++ 2008 Expression > Edition and its not working. > When I execute splint it gives me the following log.Sorry for > including this long log here. > splint has not even touch the source code that I have written. > Thanks in advance,AJ > > [ > Command Line: Cannot open options file: C:\Program > There was a problem reading an initialization file (Use -warnrc to > inhibit > warning) You need quotation marks around "Program Files" End of story. (The Open Watcom C/C++ and Fortran 77 compilers have similar troubles with spaces in file names, which is why they install in C:\WATCOM instead of C:\Program Files\WATCOM.) > From ok at cs.otago.ac.nz Mon Mar 15 17:54:01 2010 From: ok at cs.otago.ac.nz (Richard O'Keefe) Date: Tue, 16 Mar 2010 11:54:01 +1300 Subject: [splint-discuss] Newbie in Splint world In-Reply-To: <35b67cf61003150112j48761e1fx46469ed86cdceb4f@mail.gmail.com> References: <35b67cf61003150112j48761e1fx46469ed86cdceb4f@mail.gmail.com> Message-ID: <9724E77D-2F41-4A0D-A1C3-FFDF1F5238C3@cs.otago.ac.nz> On Mar 15, 2010, at 9:12 PM, A Z wrote: > Guys > Just started to use splint in IDE of Visual C++ 2008 Expression > Edition and its not working. > When I execute splint it gives me the following log.Sorry for > including this long log here. > splint has not even touch the source code that I have written. > Thanks in advance,AJ > > [ > Command Line: Cannot open options file: C:\Program > There was a problem reading an initialization file (Use -warnrc to > inhibit > warning) You need quotation marks around "Program Files" End of story. (The Open Watcom C/C++ and Fortran 77 compilers have similar troubles with spaces in file names, which is why they install in C:\WATCOM instead of C:\Program Files\WATCOM.) > From newlifewithg at gmail.com Mon Mar 15 23:44:06 2010 From: newlifewithg at gmail.com (A Z) Date: Tue, 16 Mar 2010 13:44:06 +0900 Subject: [splint-discuss] splint-discuss Digest, Vol 65, Issue 3 In-Reply-To: References: Message-ID: <35b67cf61003152144t2178aeeyce206c0f71fbeec2@mail.gmail.com> Michael Thanks. About command line problem: I followed [> splint -f "c:\program files\splint-3.1.1\bin\.splintrc"] and it is working fine.Thanks. About other errors: > These other errors could be cascades from the failure to load your > .splintrc Here is my .splintrc settings: -I. -IC:/include -D_M_IX86=400 -DWIN32 -D_NTSYSTEM -D_WIN32_WINNT=0x0400 -DWINVER=600 -DNOGDI -DNOKERNEL -DNOUSER -DWIN32_LEAN_AND_MEAN -likelybool -D__int64=long -D_int64=int -D_wtoi=atoi -DSTRICT Have no idea what does this settings has to do ?Just followed the page below for set-up http://www.splint.org/vc.splintrc > > > ------------------------------ > > Message: 2 > Date: Mon, 15 Mar 2010 06:47:28 -0700 > From: "Michael Wojcik" > Subject: Re: [splint-discuss] Newbie in Splint world > To: "Discussions about the Splint annotation-assisted static > ? ? ? ?analysisproject" ? ? ? ? > Message-ID: > ? ? ? ?<81F42F63D5BB344ABF294F8E80990C7902782425 at MTV-EXCHANGE.microfocus.com> > Content-Type: text/plain; ? ? ? charset="us-ascii" > >> From: splint-discuss-bounces at cs.virginia.edu [mailto:splint-discuss- >> bounces at cs.virginia.edu] On Behalf Of A Z >> Sent: Monday, 15 March, 2010 04:12 >> >> Guys >> Just started to use splint in IDE of ?Visual C++ 2008 Expression >> Edition and its not working. > > Using it under an IDE may not be the best plan. You'll have an easier > time controlling the command line and environment running Splint from a > console window. > >> When I execute splint it gives me the following log.Sorry for > including >> this long log here. >> >> [ >> Command Line: Cannot open options file: C:\Program >> ? There was a problem reading an initialization file (Use -warnrc to > inhibit >> ? warning) >> Command Line: Unrecognized file extension: >> ? ? Files\splint-3.1.1\bin\.splintrc (assuming .splintrc is C source > code) >> ? warn when command line file does not have a recognized extension > (Use >> ? -fileextensions to inhibit warning) > > You have spacey path names on the Splint command line, and they're not > quoted. > > Here, the problem is a command line like: > > ? ? splint -f C:\Program Files\splint-3.1.1\bin\.splintrc > > Like all good programs, splint uses spaces as delimiters on its command > line, so it reads that as "-f C:\Program", followed by another argument > that's "Files\splint-3.1.1\bin\.splintrc". > > Arguments with spaces in the name need to be quoted: > > ? ? splint -f "c:\program files\splint-3.1.1\bin\.splintrc" > > Even better, do not use spacey paths, as they are a brain-dead > convention introduced by Microsoft to make everyone's life harder. > Install Splint in a sensible, spaceless path, and keep your sources in a > similar one. > >> C:\include\vadefs.h(52,26): Datatype uintptr_t declared with >> inconsistent type: >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?unsigned int >> ? A function, variable or constant is redefined with a different type. >> (Use >> ? -incondefs to inhibit warning) >> ? ?load file standard.lcd: Specification of uintptr_t: unsigned int * > > These other errors could be cascades from the failure to load your > .splintrc, or they could be real problems with your source. There's no > way for us to tell, since we cannot psychically see what in your source > is producing them. > > -- > Michael Wojcik > Principal Software Systems Developer, Micro Focus > > > > > ------------------------------ > > _______________________________________________ > splint-discuss mailing list > splint-discuss at mail.cs.virginia.edu > http://www.cs.virginia.edu/mailman/listinfo/splint-discuss > > > End of splint-discuss Digest, Vol 65, Issue 3 > ********************************************* > From splint at sympatico.ca Wed Mar 17 00:01:22 2010 From: splint at sympatico.ca (Bill Pringlemeir) Date: Wed, 17 Mar 2010 00:01:22 -0500 Subject: [splint-discuss] Cgrammar.c: yypact[], yydefgoto[], yyr1[], yydefact[], yyr2[] References: <4B8E6E8A.2070707@cs.virginia.edu> <4B8E7829.4030903@cs.virginia.edu> Message-ID: <87tysfh78d.fsf@sympatico.ca> On 9 Mar 2010, muneeswaranp at hcl.in wrote: > 2. Is it generated automatically from bison utility ? Is it done manually ? Yes. Yes. You can delete the '.der' files and the build system will then require bison (yacc) to rebuild the files. You can look at the Makefile that is generated with automake, aclocal, autoconf, etc. The '.der' files are committed to CVS so that people aren't required to have bison to build splint. hth, Bill Pringlemeir. -- Little girls, like butterflies need no excuses. - Robert Heinlein From splint at sympatico.ca Wed Mar 17 00:01:22 2010 From: splint at sympatico.ca (Bill Pringlemeir) Date: Wed, 17 Mar 2010 00:01:22 -0500 Subject: [splint-discuss] Cgrammar.c: yypact[], yydefgoto[], yyr1[], yydefact[], yyr2[] References: <4B8E6E8A.2070707@cs.virginia.edu> <4B8E7829.4030903@cs.virginia.edu> Message-ID: <87tysfh78d.fsf@sympatico.ca> On 9 Mar 2010, muneeswaranp at hcl.in wrote: > 2. Is it generated automatically from bison utility ? Is it done manually ? Yes. Yes. You can delete the '.der' files and the build system will then require bison (yacc) to rebuild the files. You can look at the Makefile that is generated with automake, aclocal, autoconf, etc. The '.der' files are committed to CVS so that people aren't required to have bison to build splint. hth, Bill Pringlemeir. -- Little girls, like butterflies need no excuses. - Robert Heinlein From splint at sympatico.ca Wed Mar 17 00:01:22 2010 From: splint at sympatico.ca (Bill Pringlemeir) Date: Wed, 17 Mar 2010 00:01:22 -0500 Subject: [splint-discuss] Cgrammar.c: yypact[], yydefgoto[], yyr1[], yydefact[], yyr2[] References: <4B8E6E8A.2070707@cs.virginia.edu> <4B8E7829.4030903@cs.virginia.edu> Message-ID: <87tysfh78d.fsf@sympatico.ca> On 9 Mar 2010, muneeswaranp at hcl.in wrote: > 2. Is it generated automatically from bison utility ? Is it done manually ? Yes. Yes. You can delete the '.der' files and the build system will then require bison (yacc) to rebuild the files. You can look at the Makefile that is generated with automake, aclocal, autoconf, etc. The '.der' files are committed to CVS so that people aren't required to have bison to build splint. hth, Bill Pringlemeir. -- Little girls, like butterflies need no excuses. - Robert Heinlein From waltergoossens at home.nl Mon Mar 22 05:11:39 2010 From: waltergoossens at home.nl (waltergoossens at home.nl) Date: Mon, 22 Mar 2010 10:11:39 +0000 (GMT) Subject: [splint-discuss] Small patch Message-ID: Hi list, Using splint I found that the "hh" modifier in sscanf is not supported. Attached is a patch to add this. I'm not quite sure if this is the right place to send this patch to but splint seems mostly abandoned so I thought this might help a bit reviving a great project! Greetz Walter PS: If no-one has time/interrest in accepting patches like this, I'll volunteer to step up, not being a hard-core splint guru but willing to learn. From waltergoossens at home.nl Mon Mar 22 06:06:44 2010 From: waltergoossens at home.nl (waltergoossens at home.nl) Date: Mon, 22 Mar 2010 11:06:44 +0000 (GMT) Subject: [splint-discuss] Small patch In-Reply-To: References: Message-ID: Hmm WITH patch this time... ----- Origineel bericht ----- Van: waltergoossens at home.nl Datum: maandag, maart 22, 2010 10:33 Onderwerp: [splint-discuss] Small patch Aan: splint-discuss at mail.cs.virginia.edu > Hi list, > > Using splint I found that the "hh" modifier in sscanf is not > supported. Attached is a patch to add this. I'm not quite sure if this > is the right place to send this patch to but splint seems mostly > abandoned so I thought this might help a bit reviving a great project! > > Greetz > Walter > > PS: If no-one has time/interrest in accepting patches like this, I'll > volunteer to step up, not being a hard-core splint guru but willing to > learn. > _______________________________________________ > splint-discuss mailing list > splint-discuss at mail.cs.virginia.edu > http://www.cs.virginia.edu/mailman/listinfo/splint-discuss -------------- next part -------------- A non-text attachment was scrubbed... Name: splint_sscanf_doubleh_support.patch Type: text/x-diff Size: 827 bytes Desc: not available Url : http://www.cs.virginia.edu/pipermail/splint-discuss/attachments/20100322/c962a076/attachment.bin From splint at sympatico.ca Thu Mar 25 10:23:55 2010 From: splint at sympatico.ca (Bill Pringlemeir) Date: Thu, 25 Mar 2010 11:23:55 -0400 Subject: [splint-discuss] Is it possible to dump static variable type information In-Reply-To: <5e9e5cab1002191453t75545968n7b3c1a60573ae176@mail.gmail.com> (Michael Bauer's message of "Fri, 19 Feb 2010 22:53:12 +0000") References: <5e9e5cab1002191453t75545968n7b3c1a60573ae176@mail.gmail.com> Message-ID: <87sk7oo25w.fsf@sympatico.ca> On 19 Feb 2010, mvbauer at gmail.com wrote: > I have a desire to determine the primitive type for all static variables > in my program.* I believe that SPLINT is already parsing my variables in > order to do type checking.* I am wondering if there is an option to dump > this information into a file?* Any ideas are much appreciated. There is the option '+keep' which places a pre-processed variant of all files in 'tmp'. 'grep', 'sort', and 'uniq' can probably process this output to get what you want. Although, i think that the program 'ctags' already has something like this. I would try the '-x' and '-g' options. hth, Bill Pringlemeir. -- Yow! Legally-imposed CULTURE-reduction is CABBAGE-BRAINED! From garyyang6 at yahoo.com Fri Mar 26 15:40:22 2010 From: garyyang6 at yahoo.com (Gary Yang) Date: Fri, 26 Mar 2010 13:40:22 -0700 (PDT) Subject: [splint-discuss] How to insert splint into Makefile for Linux compilation Message-ID: <886571.86335.qm@web37906.mail.mud.yahoo.com> Hi, I am working on linux-2.6.25. I would like to use splint when I compile linux-2.6.25. At one of the source directory, I typed "splint *.c". I got "Cannot find include file", "Cannot continue". I understand that I need to run splint inside the Makefile so that it will find the correct include files. However, how to insert splint info Makefile? Anyone has any idea? splint *.c Splint 3.1.2 --- 24 Mar 2010 cache.c:7:25: Cannot find include file asm/pgtable.h on search path: /usr/include;/usr/local/include Preprocessing error. (Use -preproc to inhibit warning) cache.c:42:27: #error Unknown cache type. Preprocessing error for file: /projects/svdc/P4wsIPCSW/buildsw_canyonlands/linux /arch/m32r/mm/cache.c *** Cannot continue. Thanks, Gary From jhanley at dgtlrift.com Fri Mar 26 21:02:56 2010 From: jhanley at dgtlrift.com (James Hanley) Date: Fri, 26 Mar 2010 22:02:56 -0400 Subject: [splint-discuss] How to insert splint into Makefile for Linux compilation In-Reply-To: <886571.86335.qm@web37906.mail.mud.yahoo.com> References: <886571.86335.qm@web37906.mail.mud.yahoo.com> Message-ID: <4660FD82-2C85-4482-932D-EB40D64D1DD6@dgtlrift.com> You have to set up a rule that creates an intermediate depency before the object file dependancy. The author of gsml - he has some great tricks for make files. On Mar 26, 2010, at 4:40 PM, Gary Yang wrote: > Hi, > > I am working on linux-2.6.25. I would like to use splint when I > compile linux-2.6.25. At one of the source directory, I typed > "splint *.c". I got "Cannot find include file", "Cannot continue". I > understand that I need to run splint inside the Makefile so that it > will find the correct include files. However, how to insert splint > info Makefile? Anyone has any idea? > > > splint *.c > Splint 3.1.2 --- 24 Mar 2010 > > cache.c:7:25: Cannot find include file asm/pgtable.h on search path: > /usr/include;/usr/local/include > Preprocessing error. (Use -preproc to inhibit warning) > cache.c:42:27: #error Unknown cache type. > Preprocessing error for file: /projects/svdc/P4wsIPCSW/ > buildsw_canyonlands/linux > /arch/m32r/mm/cache.c > *** Cannot continue. > > > Thanks, > > > Gary > > > > > > > _______________________________________________ > splint-discuss mailing list > splint-discuss at mail.cs.virginia.edu > http://www.cs.virginia.edu/mailman/listinfo/splint-discuss From n3npq at mac.com Sat Mar 27 07:18:33 2010 From: n3npq at mac.com (Jeff Johnson) Date: Sat, 27 Mar 2010 08:18:33 -0400 Subject: [splint-discuss] API-sanity-autotest using splint annotations Message-ID: <985E7455-213F-4B5E-A57A-7B009F0886EC@mac.com> The latest Api-sanity-autotest.pl 1.7 release now includes a -splint-specs option that can use some splint annotations to generate unit tests. Details of API-sanity-autotest are available here: http://ispras.linuxfoundation.org/index.php/API_Sanity_Autotest As unit test harnesses go (IMHO), api-sanity-autotest.pl is quite simple to use for "shallow" testing (i.e. call every routine in an API with (reasonable in most, but not all, cases) inputs. And there is markup to write "specialized types" for better test generation. FYI 73 de Jeff