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] Named behavior, proof obligations and ACSL annotations: the string comparison example
- Subject: [Frama-c-discuss] Named behavior, proof obligations and ACSL annotations: the string comparison example
- From: Claude.Marche at inria.fr (Claude Marché)
- Date: Thu, 26 Mar 2009 17:19:45 +0100
- In-reply-to: <F1229212CB084F4CBEA197909C8699F1021BD98E@TLSMAIL1.tls.fr.astrium.corp>
- References: <F1229212CB084F4CBEA197909C8699F1021BD98D@TLSMAIL1.tls.fr.astrium.corp> <49CB9CDF.8070301@inria.fr> <F1229212CB084F4CBEA197909C8699F1021BD98E@TLSMAIL1.tls.fr.astrium.corp>
I guess there is also a tricky point, because the way your code is written. Using directly return statements without using the diff variable should make things simpler. With the diff variable, it might be necessary to specify that diff is not modified in the loop... (i.e remains 0) sorry I can't help more without running the example and see precisely what VC are not proved. - Claude PAREAUD, Thomas wrote: > Thank you for this answer. > > Is the 3) point is equivalent to add the predicate below in the loop invariant declaration? > > loop invariant > [...] > && \forall integer k ; 0 <= k < (\at(nbBytes, Pre) - nbBytes) ==> (*(\at(pString1, Pre)+k) == *(\at(pString2, Pre)+k)); > > This line is equivalent to the following one: > > \forall integer k ; 0 <= k < (\at(nbBytes, Pre) - nbBytes) ==> (*(pString1-k) == *(pString2-k)); > > > But none of the two solutions makes solver proving anything. > > Have you any other idea? > -- > Thomas Pareaud > > > > > -----Message d'origine----- > De : frama-c-discuss-bounces at lists.gforge.inria.fr [mailto:frama-c-discuss-bounces at lists.gforge.inria.fr] De la part de Claude March? > Envoy? : jeudi 26 mars 2009 16:19 > ? : Frama-C public discussion > Objet : Re: [Frama-c-discuss] Named behavior, proof obligations and ACSL annotations: the string comparison example > > A few hints: > > 1) use integer instead of int in annotations. It will probably not help, > but is better practice > > 2) split the identity into two, w.r.t your disjunction. > > 3) add a loop invariant expressing that the chars visited so far are > equal, otherwise you will not be able to prove anything. > > - Claude > > PAREAUD, Thomas wrote: >> Dear all, >> >> I am a recent user of Frama-C and its Jessie plug-in. >> I tried for several days to train to this tool. >> >> Below, there is an example of a function that compare two strings. >> There are four different behaviors: >> - zero: the number of byte to compare equals 0 (return 0) >> - identity: the two strings are identical (return 0) >> - positive: it exists a position such as every char before this position >> were identical between the two strings, and the char at this position is >> greater in the first string that in the second one. >> - negative: it exists a position such as every char before this position >> were identical between the two strings, and the char at this position is >> lower in the first string that in the second one. >> >> I managed to prove the "Safety" (verified by the Yices solver thanks to >> the loop invariant I introduced) and "zero" behaviors. >> Nevertheless, I did not manage to prove neither identity, nor positive, >> nor negative behaviors. >> >> You can find the detail of the code and ACSL annotations below. >> >> Does someone have a proposition? >> >> Best regards, >> -- >> Thomas Pareaud >> >> >> >> /*@ requires nbBytes >= 0; >> @ requires \valid(pString1 + (0..(nbBytes-1))); >> @ requires \valid(pString2 + (0..(nbBytes-1))); >> @ requires nbBytes!=0 ==> \exists int j ; 0<=j<nbBytes && >> *(pString1+j)==0; >> @ requires nbBytes!=0 ==> \exists int j ; 0<=j<nbBytes && >> *(pString2+j)==0; >> @ assigns \nothing; >> @ behavior zero: >> @ assumes nbBytes == 0; >> @ ensures \result == 0; >> @ behavior identity: >> @ assumes >> @ nbBytes > 0 >> @ && ( >> @ (\forall int i; 0<=i<nbBytes ==> *(pString1+i)==*(pString2+i)) >> @ || (\exists int j; 0<=j<nbBytes && *(pString1+j)==0 && >> (\forall int i; 0<=i<=j ==> *(pString1+i)==*(pString2+i))) >> @ ); >> @ ensures \result == 0; >> @ behavior postive: >> @ assumes nbBytes > 0 && \exists int j; *(pString1+j)>*(pString2+j) >> && (\forall int i; 0<=i<j<nbBytes ==> *(pString1+i)==*(pString2+i)); >> @ ensures \result > 0; >> @ behavior negative: >> @ assumes nbBytes > 0 && \exists int j; *(pString1+j)<*(pString2+j) >> && (\forall int i; 0<=i<j<nbBytes ==> *(pString1+i)==*(pString2+i)); >> @ ensures \result < 0; >> @ disjoint behaviors zero, identity, non_identity; >> */ >> int strncmp(const char *pString1, const char *pString2, unsigned int >> nbBytes) >> { >> int diff = 0; >> >> if (nbBytes == 0) >> { >> diff = 0; >> } >> else >> { >> /*@ loop invariant >> @ 0 < nbBytes <= \at(nbBytes, Pre) >> @ && \at(pString1, Pre) + \at(nbBytes, Pre) == pString1 + nbBytes >> @ && \at(pString2, Pre) + \at(nbBytes, Pre) == pString2 + nbBytes ; >> @ loop assigns \nothing; >> @ loop variant nbBytes; >> */ >> while ((nbBytes-- != 0) && (*pString1 == *pString2)) >> { >> if ((nbBytes == 0) || (*pString1 == '\0')){ >> break; >> } >> pString1++; >> pString2++; >> } >> diff = (((int)*pString1) - ((int)*pString2)); >> } >> >> return diff; >> } >> >> >> Ce courriel (incluant ses eventuelles pieces jointes) peut contenir des informations confidentielles et/ou protegees ou dont la diffusion est restreinte. Si vous avez recu ce courriel par erreur, vous ne devez ni le copier, ni l'utiliser, ni en divulguer le contenu a quiconque. Merci d'en avertir immediatement l'expediteur et d'effacer ce courriel de votre systeme. Astrium decline toute responsabilite en cas de corruption par virus, d'alteration ou de falsification de ce courriel lors de sa transmission par voie electronique. >> This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. >> --------------------------------------------------------------------- >> Astrium SAS (393 341 516 RCS Paris) - Siege social: 6 rue Laurent Pichat, 75016 Paris, France >> >> _______________________________________________ >> Frama-c-discuss mailing list >> Frama-c-discuss at lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/frama-c-discuss > -- Claude March? | tel: +33 1 72 92 59 69 INRIA Saclay - ?le-de-France | mobile: +33 6 33 14 57 93 Parc Orsay Universit? | fax: +33 1 74 85 42 29 4, rue Jacques Monod - B?timent N | http://www.lri.fr/~marche/ F-91893 ORSAY Cedex |
- Follow-Ups:
- [Frama-c-discuss] Named behavior, proof obligations and ACSL annotations: the string comparison example
- From: Thomas.PAREAUD at astrium.eads.net (PAREAUD, Thomas)
- [Frama-c-discuss] Named behavior, proof obligations and ACSL annotations: the string comparison example
- References:
- [Frama-c-discuss] Named behavior, proof obligations and ACSL annotations: the string comparison example
- From: Thomas.PAREAUD at astrium.eads.net (PAREAUD, Thomas)
- [Frama-c-discuss] Named behavior, proof obligations and ACSL annotations: the string comparison example
- From: Claude.Marche at inria.fr (Claude Marché)
- [Frama-c-discuss] Named behavior, proof obligations and ACSL annotations: the string comparison example
- From: Thomas.PAREAUD at astrium.eads.net (PAREAUD, Thomas)
- [Frama-c-discuss] Named behavior, proof obligations and ACSL annotations: the string comparison example
- Prev by Date: [Frama-c-discuss] Named behavior, proof obligations and ACSL annotations: the string comparison example
- Next by Date: [Frama-c-discuss] Named behavior, proof obligations and ACSL annotations: the string comparison example
- Previous by thread: [Frama-c-discuss] Named behavior, proof obligations and ACSL annotations: the string comparison example
- Next by thread: [Frama-c-discuss] Named behavior, proof obligations and ACSL annotations: the string comparison example
- Index(es):