From: Timur Tabi <timur@kernel.org>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: cocci <cocci@systeme.lip6.fr>, Timur Tabi <timur@kernel.org>
Subject: Re: [Cocci] Fatal exception in spatch when #include file does not exist
Date: Tue, 22 Jan 2019 16:06:02 -0600 [thread overview]
Message-ID: <CAOZdJXWTzvTJFrdUnWD-YPPj6o=k2Xum5PR6enZKutv_+TRrEQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1901222147550.2519@hadrien>
On Tue, Jan 22, 2019 at 2:48 PM Julia Lawall <julia.lawall@lip6.fr> wrote:
> It finds type information. It also matches your rules against the
> definitions found in the header files, just like it matches the rules
> against the definitions found in the .c files.
What happens when it matches a rule in a header file? Does that mean
that it will try to edit the header file as well?
It seems to me for my DBG_PRINTF changes, I definitely want --no-includes.
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-01-22 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 19:31 [Cocci] Fatal exception in spatch when #include file does not exist Timur Tabi
2019-01-22 19:44 ` Julia Lawall
2019-01-22 20:39 ` Timur Tabi
2019-01-22 20:48 ` Julia Lawall
2019-01-22 22:06 ` Timur Tabi [this message]
[not found] ` <b73ba628-ee07-5962-0f17-72cebfa14954@users.sourceforge.net>
2019-01-23 16:14 ` [Cocci] Source code adjustments in header files? Timur Tabi
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='CAOZdJXWTzvTJFrdUnWD-YPPj6o=k2Xum5PR6enZKutv_+TRrEQ@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).