--- layout: fc_discuss_archives title: Message 40 from Frama-C-discuss on March 2009 ---
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] Dead code that shouldn't be



Hi,

I'm back with this problem.

I managed to patch nullhttpd so that I could perform the analysis I
wanted to.

Now, I want to use frama-c to analyse something way bigger than
nullhttpd, so I was wondering if it would be possible (and if it was any
relevant) to tell frama-c to ignore those probable run-time errors and
continue the analysis ?

Thanks.

On Wed, 2008-12-12 at 03:25 +0100, Pascal Cuoq wrote:
> This is what happens when a missing bit of context makes the
> analyzer believe that a run-time error certainly happens quickly.
> ...
> One way to locate the instruction where it wrongly thinks that
> a run-time error certainly happens is to follow the control flow
> until the first dead statement in the gui.