Frama-C-discuss mailing list archives

This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] patchFile

  • Subject: [Frama-c-discuss] patchFile
  • From: WPineault at (Wayne Pineault)
  • Date: Wed, 11 Apr 2012 20:44:04 +0000
  • In-reply-to: <>
  • References: <>, <>

Hi Boris,

I have made huge changes to the share directory .c and .h files to get some of my plugins to work correctly.

I have tried the -nostdinc directive (and this was my 4'th worst fix) but I currently have 12424 headers in my /usr/include directories and didn't want to provide a copy of all of these!

I think that what I will do is edit the files that I need and save them in /tmp and then run frama-c on those files from their originating directory since it seems that the local include files will still be used.

I am still on Fedora 14, I tried to compile Boron on a Fedora core 16 and the libraries that it needed were not found.  What Linux version does Nitrogen compile on?


From: frama-c-discuss-bounces at [frama-c-discuss-bounces at] on behalf of Boris Yakobowski [boris at]
Sent: Wednesday, April 11, 2012 2:04 PM
To: Frama-C public discussion
Subject: Re: [Frama-c-discuss] patchFile


On Wed, Apr 11, 2012 at 4:20 PM, Wayne Pineault <WPineault at> wrote:
> My goal is to analyse C code without modifying the original source code.  I
> want to get rid of all the #include <filename.h> directives since Frama-C
> value analysis does not work properly with these files included.

Not including headers is a bad idea in general. Although Frama-C may
parse a code in which a function is used before having been declared,
the implicit declaration mechanism present in ANSI C will sometimes
lead to subtly broken abstract syntax trees.

Are the <filename.h> files you wish to skip those of the standard C
library? If so, did you try gcc's option "-nostdinc" (or the
equivalent one for your preprocessor); using the headers of your
system is almost always a bad idea. You can also try to include the
standard library which is packaged by Frama-C (and installed in
$SHARE/frama-c/libc), but before doing so, you should really upgrade
to Nitrogen.

Hope this helps,


Frama-c-discuss mailing list
Frama-c-discuss at