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] approximations in value analysis

  • Subject: [Frama-c-discuss] approximations in value analysis
  • From: sali.sene at (SENE, Sali)
  • Date: Thu, 7 Jul 2011 09:25:02 +0200

Hi all,

I have many approximations in the result of my analysis. Some of this approximations are caused by arithmetic on variable pointer.

Like this:
sources/alloc_new.c:59:[value] reading left-value new.
        It contains a garbled mix of {heap; ioctl_requests; ioctl_args; "DRIVER DSO"; }
        because of Arithmetic {sources/alloc_new.c:56; }.

The line alloc_new.c:56
new->size = (int)next - (int)new - BLOCK_SIZE;

next and new are some variable pointer.

How can I fix this approximation?


The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>