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] integer overflow
- Subject: [Frama-c-discuss] integer overflow
- From: Pascal.Cuoq at cea.fr (Pascal Cuoq)
- Date: Fri, 12 Jun 2009 13:50:00 +0200
- In-reply-to: <627CD66B-9735-4F0C-8AC2-364A69853F56@cea.fr>
- References: <4A315C7C.3030309@cs.utah.edu> <5EFD4D7AC6265F4D9D3A849CEA9219191AB1DB@LAXA.intra.cea.fr> <4A3170BD.6080802@cs.utah.edu> <627CD66B-9735-4F0C-8AC2-364A69853F56@cea.fr>
>> >> Running Frama-C's value analysis gives this: >> >> Values for function foo: >> tmp ? {0; } >> __retres ? {0; } >> >> If I understand correctly, this means that the function must return >> 0. > > For test programs that are destined to be both analyzed and executed, > I agree that our handling of printf is not the best. You can confirm > that > the temporary variable tmp indeeds holds the value of foo(-2) by > inspecting the normalized source code ("frama-c test.c -print"). And trying my own advice after sending it to the list, I realize that I got it wrong and that it is __retres that holds the return value of foo. Facepalm. Pascal -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? enlev?e... URL: http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20090612/3a4cdf76/attachment.htm
- References:
- [Frama-c-discuss] integer overflow
- From: regehr at cs.utah.edu (John Regehr)
- [Frama-c-discuss] integer overflow
- From: Pascal.CUOQ at cea.fr (CUOQ Pascal)
- [Frama-c-discuss] integer overflow
- From: regehr at cs.utah.edu (John Regehr)
- [Frama-c-discuss] integer overflow
- From: Pascal.Cuoq at cea.fr (Pascal Cuoq)
- [Frama-c-discuss] integer overflow
- Prev by Date: [Frama-c-discuss] integer overflow
- Next by Date: [Frama-c-discuss] integer overflow
- Previous by thread: [Frama-c-discuss] integer overflow
- Next by thread: [Frama-c-discuss] integer overflow
- Index(es):