From: Julia Lawall <julia.lawall@lip6.fr>
To: Timur Tabi <timur@kernel.org>
Cc: cocci <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Fatal error: exception File "engine/ctlcocci_integration.ml", line 361, characters 4-10: Assertion failed
Date: Fri, 7 Dec 2018 18:42:17 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1812071837160.20798@hadrien> (raw)
In-Reply-To: <CAOZdJXW9XmFAPbhiSsejhFZ+9me=kHc25A-Qk0e=CrCnkkFuhw@mail.gmail.com>
On Fri, 7 Dec 2018, Timur Tabi wrote:
> spatch version 1.0.7-00117-g163d2058 compiled with OCaml version 4.05.0
> Flags passed to the configure script: --disable-parmap
> OCaml scripting support: yes
> Python scripting support: yes
> Syntax of regular expresssions: PCRE
>
> Unfortunately, I can't share the C source file, and the --debug option
> to spatch doesn't display anything. This is a self-built spatch (with
> parmap disabled), and line 361's assertion is:
>
> F.KeyMap.iter (fun nodei node ->
> assert (F.KeyEdgeSet.cardinal (!g#successors nodei) >= 1);
> ) !g#nodes;
>
> I can't understand this code, so I can't debug it myself.
Do you know which function in your C code causes the problem? Does that
function have some dead code? You can try
spatch --control-flow file.c
and see if there is anything suspicious. You may need to reduce the
number of functions in the file or the number of lines of code in the
functions.
julia
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2018-12-07 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 17:17 [Cocci] Fatal error: exception File "engine/ctlcocci_integration.ml", line 361, characters 4-10: Assertion failed Timur Tabi
2018-12-07 17:42 ` Julia Lawall [this message]
2018-12-07 17:51 ` Timur Tabi
2018-12-07 17:55 ` Julia Lawall
2018-12-07 17:56 ` Julia Lawall
2018-12-07 18:17 ` Timur Tabi
2018-12-07 18:20 ` Julia Lawall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1812071837160.20798@hadrien \
--to=julia.lawall@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=timur@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).