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] [jessie-plugin] cannot be used on your code


  • Subject: [Frama-c-discuss] [jessie-plugin] cannot be used on your code
  • From: Claude.Marche at inria.fr (Claude Marche)
  • Date: Thu, 17 May 2012 19:06:38 +0200
  • In-reply-to: <4FB52125.1090505@free.fr>
  • References: <mailman.29.1336989688.28070.frama-c-discuss@lists.gforge.inria.fr> <4FB52125.1090505@free.fr>

See http://lists.gforge.inria.fr/pipermail/why-discuss/2008-June/000054.html

On 05/17/2012 06:02 PM, dams wrote:
>
> which is a simple test. Then I've got a recurrent  error :
> frama-c -jessie test.c
> [kernel] preprocessing with "gcc -C -E -I.  -dD test.c"
> [jessie] Starting Jessie translation
> [jessie] Producing Jessie files in subdir test.jessie
> [jessie] File test.jessie/test.jc written.
> [jessie] File test.jessie/test.cloc written.
> [jessie] Calling Jessie tool in subdir test.jessie
> Generating Why function test
> Generating Why function main
> [jessie] Calling VCs generator.
> gwhy-bin [...] why/test.why
> Computation of VCs...
> Computation of VCs done.
> Reading GWhy configuration...
> Loading .gwhyrc config file
> GWhy configuration loaded...
> Creating GWhy Tree view...
> GWhy Tree view created...
> Creating GWhy views...
> Segmentation fault