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] A question on Frama-C input/output analysis

  • Subject: [Frama-c-discuss] A question on Frama-C input/output analysis
  • From: haihaoshen at gmail.com (haihao shen)
  • Date: Sat, 5 Mar 2011 16:15:43 +0800
  • In-reply-to: <AANLkTi=36g3OtSaVJ=Hm_qtJueF+0g1DCwseLAQx8kVf@mail.gmail.com>
  • References: <AANLkTi=36g3OtSaVJ=Hm_qtJueF+0g1DCwseLAQx8kVf@mail.gmail.com>
 Hi,

Recently I used Frama-C to analyze the input/output information for each C
function. However, I found for some functions, there are many inputs (more
than 200, but most of them are similar).

Here is one sample input, and hope that you could help me figure out why
these are generated by Frama-C.

##star_star_star_xx_pointer_0nth__inner_pointer_0nth__field[bits 0 to
549755813887]## xx_pointer is one of pointers used in a function,
inner_pointer is a field of structure, pointed by xx_pointer, while field is
a field of structure, pointed by inner_pointer.

Since there are many similar inputs, I am wondering whether they are really
inputs for a function.

Any comments are welcome!

Thanks,
Haihao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20110305/61da39f8/attachment.htm>