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] Frama-c flag -stop-at-first-alarm 'unknown'

  • Subject: [Frama-c-discuss] Frama-c flag -stop-at-first-alarm 'unknown'
  • From: boris at yakobowski.org (Boris Yakobowski)
  • Date: Thu, 1 Dec 2016 10:42:11 +0100
  • In-reply-to: <CALOET+DmhV93kiH9hgTpYFqLS33U7f9VzAE7iZ=cWerxiUru7Q@mail.gmail.com>
  • References: <CALOET+AOrZQPWF8VFOy6gGkGxBxVhmkTCedVxKrTx9aLV8Lj9Q@mail.gmail.com> <0f742ff3-8fbb-f5ef-0ece-74460e6ae3d3@cea.fr> <CALOET+DmhV93kiH9hgTpYFqLS33U7f9VzAE7iZ=cWerxiUru7Q@mail.gmail.com>
Hi Faraz,

The documentation of several options of Value is indeed lacking, mainly due
to their sheer number and lack of time.  *-val-stop-at-nth-alarm * is also
a bit weird, in that the same alarm may be counted multiple times. The
meaning of n is thus particularly unclear...

Currently all existing documentation can be found either within Value's
manual, or in the posts tagged *value* in the blog (
http://blog.frama-c.com/index.php?tag/value)

HTH

*,*

On Mon, Nov 28, 2016 at 11:38 PM, Faraz Hussain <fh.faraz.hussain at gmail.com>
wrote:

> Thanks Andre.  I was able to find it using 'value-help': *-val-stop-at-nth-alarm
> <n>*
>
> For the future, where can I find details about the meaning of options
> provided for a particular analysis? I couldn't find '*val-stop-at-nth-alarm'
> *in the framac user manual or the documentation for value-analysis.
>
>
> Faraz.
>
>
> On Mon, Nov 28, 2016 at 1:04 AM, Andre Maroneze <
> Andre.OLIVEIRAMARONEZE at cea.fr> wrote:
>
>> Hello,
>>
>> That option has been renamed to `-stop-at-nth-alarm 1`.
>>
>> Note that several other options have changed since the C-Reduce webpage
>> was made, so it is unlikely that the script will work without further
>> changes. Unfortunately it did not say which version of Frama-C it was
>> written with, so the phrase "which assumes that you have installed the
>> latest version of Frama-C" is no longer up-to-date. Still, most options
>> should be findable via `frama-c -kernel-help`, `frama-c -value-help`, or
>> via the Changelog (unless the renaming was forgotten).
>>
>>
>> On 27/11/2016 22:31, Faraz Hussain wrote:
>>
>> Hi,
>>
>> I'm a new user trying to use frama-c ver. Magnesium-20151002 (installed
>> via an Ubuntu 16.04 package).  I was able to successfully execute the
>> following command:
>>
>> *frama-c "-cpp-extra-args=-I ." -val -obviously-terminates -machdep
>> x86_64   file.c*
>>
>> I want to use the  flag -stop-at-first-alarm as shown in this script (
>> https://embed.cs.utah.edu/creduce/using/wrong1/test2.sh). However, on
>> doing that I get the message below:
>>
>> *[kernel] user error: option `-stop-at-first-alarm' is unknown.*
>> *                     use `frama-c -help' for more information.*
>> *[kernel] Frama-C aborted: invalid user input.*
>>
>> Has the name of this flag been changed or is there some other issue here?
>> Thanks.
>>
>> Regards
>> Faraz.
>>
>>
>>
>>
>> _______________________________________________
>> Frama-c-discuss mailing listFrama-c-discuss at lists.gforge.inria.frhttp://lists.gforge.inria.fr/mailman/listinfo/frama-c-discuss
>>
>>
>> --
>> André Maroneze
>> Ingénieur-chercheur CEA/LIST
>> Laboratoire Sûreté et Sécurité des Logiciels
>>
>>
>> _______________________________________________
>> Frama-c-discuss mailing list
>> Frama-c-discuss at lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/mailman/listinfo/frama-c-discuss
>>
>
>
> _______________________________________________
> Frama-c-discuss mailing list
> Frama-c-discuss at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/mailman/listinfo/frama-c-discuss
>



-- 
Boris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20161201/f15f8158/attachment-0001.html>