From: Timur Tabi <timur@kernel.org>
To: Timur Tabi <timur@kernel.org>
Cc: cocci <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Can the current function name be passed to a Python snippet?
Date: Wed, 5 Dec 2018 17:27:32 -0600 [thread overview]
Message-ID: <CAOZdJXWnjAPwrvWEO58fa8O28jf8YC+yt0b46Oi3TYhXazYzJQ@mail.gmail.com> (raw)
In-Reply-To: <CAOZdJXUxWV+v5UanQXRVLpOJbxA27a_zitCeUdW4uJaqX0jWgQ@mail.gmail.com>
On Wed, Dec 5, 2018 at 1:11 PM Timur Tabi <timur@kernel.org> wrote:
>
> Never mind, I now understand how the @p1 is supposed to be used. I
> have it working now.
I spoke too soon, I'm getting a weird error:
rule starting on line 232: already tagged token:
C code context
File "/tmp/cocci_small_output-22474-8398df.c", line 43, column 23,
charpos = 1216
around = '"init_PllId: Error programming clock. Stopping script.\n"',
whole content = "init_PllId: Error
programming clock. Stopping script.\n");
Line 232 is the "depends on rule" in this snippet:
// Get rid of the function name at the beginning of the string
@script:python s4@
c << r4.c;
c2;
p1 << r4.p1;
@@
import re
f = p1[0].current_element
coccinelle.c2 = re.sub('"%s[: ]*' % f, '"', c, 1)
@depends on rules@
expression x;
constant char[] r4.c;
identifier s4.c2;
@@
NV_PRINTF2(x,
-c
+c2
,...);
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2018-12-05 23:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 20:58 [Cocci] Can the current function name be passed to a Python snippet? Timur Tabi
2018-11-15 21:29 ` Julia Lawall
2018-12-04 20:17 ` Timur Tabi
2018-12-04 20:25 ` Julia Lawall
2018-12-04 22:02 ` Timur Tabi
2018-12-04 22:19 ` Timur Tabi
2018-12-05 6:35 ` Julia Lawall
2018-12-05 17:49 ` Timur Tabi
2018-12-05 19:33 ` Julia Lawall
2018-12-05 6:34 ` Julia Lawall
2018-12-05 17:57 ` Timur Tabi
2018-12-05 18:32 ` Timur Tabi
2018-12-05 19:45 ` Julia Lawall
2018-12-05 19:11 ` Timur Tabi
2018-12-05 23:27 ` Timur Tabi [this message]
2018-12-06 6:33 ` Julia Lawall
2018-12-05 19:32 ` 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=CAOZdJXWnjAPwrvWEO58fa8O28jf8YC+yt0b46Oi3TYhXazYzJQ@mail.gmail.com \
--to=timur@kernel.org \
--cc=cocci@systeme.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).