From: Julia Lawall <julia.lawall@lip6.fr>
To: "Geyslan G. Bem" <geyslan@gmail.com>
Cc: Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Michal Marek <mmarek@suse.com>,
cocci@systeme.lip6.fr, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC BUG] coccinelle: use_after_iter parse error
Date: Sun, 6 Dec 2015 14:17:19 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.10.1512061416140.2517@hadrien> (raw)
In-Reply-To: <CAGG-pUSEKCzAtKdVnMp6mvzMRo5_49HnMcMj+wMCC+aFbU7p4w@mail.gmail.com>
On Sun, 6 Dec 2015, Geyslan G. Bem wrote:
> 2015-12-06 10:09 GMT-03:00 Geyslan G. Bem <geyslan@gmail.com>:
> > Hi maintainers,
> >
> > I'm having these error output using coccinelle.
>
> Sorry, gmail and its ctrl+enter shortcut. :/
>
> geyslan@hb ~/Projects/linux $ make coccicheck V=2 M=drivers/usb/host/
> -j4 > cocciout
> Fatal error: exception Failure("minus: parse error: \n = File
> \"./scripts/coccinelle/iterators/use_after_iter.cocci\", line 126,
> column 0, charpos = 3561\n around = '&', whole content =
> &c->member\n")
Thanks ever so much for the report. Since version 1.0.4, & cannot be in
column 0, so it would need a space in front of it. I will submit a patch.
julia
> Fatal error: exception Failure("minus: parse error: \n = File
> \"./scripts/coccinelle/iterators/use_after_iter.cocci\", line 126,
> column 0, charpos = 3561\n around = '&', whole content =
> &c->member\n")
> Fatal error: exception Failure("minus: parse error: \n = File
> \"./scripts/coccinelle/iterators/use_after_iter.cocci\", line 126,
> column 0, charpos = 3561\n around = '&', whole content =
> &c->member\n")
> Fatal error: exception Failure("minus: parse error: \n = File
> \"./scripts/coccinelle/iterators/use_after_iter.cocci\", line 126,
> column 0, charpos = 3561\n around = '&', whole content =
> &c->member\n")
> Fatal error: exception Failure("minus: parse error: \n = File
> \"./scripts/coccinelle/iterators/use_after_iter.cocci\", line 126,
> column 0, charpos = 3561\n around = '&', whole content =
> &c->member\n")
> Fatal error: exception Failure("minus: parse error: \n = File
> \"./scripts/coccinelle/iterators/use_after_iter.cocci\", line 126,
> column 0, charpos = 3561\n around = '&', whole content =
> &c->member\n")
> Fatal error: exception Failure("minus: parse error: \n = File
> \"./scripts/coccinelle/iterators/use_after_iter.cocci\", line 126,
> column 0, charpos = 3561\n around = '&', whole content =
> &c->member\n")
> Fatal error: exception Failure("minus: parse error: \n = File
> \"./scripts/coccinelle/iterators/use_after_iter.cocci\", line 126,
> column 0, charpos = 3561\n around = '&', whole content =
> &c->member\n")
>
> sizeof(<+...c...+>)
> |
> &c->member // Line 126
> |
> c = E
>
> geyslan@hb ~/Projects/linux $ spatch --version
> spatch version 1.0.4 with Python support and with PCRE support
>
>
> >
> >
> > --
> > Regards,
> >
> > Geyslan G. Bem
> > hackingbits.com
>
>
>
> --
> Regards,
>
> Geyslan G. Bem
> hackingbits.com
>
next prev parent reply other threads:[~2015-12-06 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 13:09 Geyslan G. Bem
2015-12-06 13:13 ` Geyslan G. Bem
2015-12-06 13:17 ` Julia Lawall [this message]
2015-12-06 13:27 ` Geyslan G. Bem
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.10.1512061416140.2517@hadrien \
--to=julia.lawall@lip6.fr \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=geyslan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=nicolas.palix@imag.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
all inboxes | Powered by JetHome®