From: Timur Tabi <timur@kernel.org>
To: Julia Lawall <julia.lawall@lip6.fr>
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 12:17:19 -0600 [thread overview]
Message-ID: <CAOZdJXUVc0Z0z-VmDCnjNknyeCRiebvYd2K9ePRk5qEPyzWg+Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1812071855470.20798@hadrien>
On Fri, Dec 7, 2018 at 11:56 AM Julia Lawall <julia.lawall@lip6.fr> wrote:
> I guess you run Coccinelle on a complete directory? If so, does the
> assert cause everything to crash, or only the treatment of the given file?
Only that file crashes. I changed that line to remove the ##, but it
didn't fix anything. So I just commented out the entire macro and now
spatch works on that file.
Considering the unique nature of this code, I'm not sure that there's
anything to fix. It would be nice if the normal error reporting was
more accurate, since I typically need to use --debug or not
--control-flow just to find the offending line in my C files.
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2018-12-07 18:18 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
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 [this message]
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=CAOZdJXUVc0Z0z-VmDCnjNknyeCRiebvYd2K9ePRk5qEPyzWg+Q@mail.gmail.com \
--to=timur@kernel.org \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@lip6.fr \
/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).