From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Checking for null pointers
Date: Sat, 09 May 2015 09:11:57 +0200 [thread overview]
Message-ID: <554DB33D.2000000@users.sourceforge.net> (raw)
In-Reply-To: <CABBGRWueC78515AqDfkX4buzjipbkNhAvZ5G5OAkWhX+4WwAuA@mail.gmail.com>
> I am asking you if you can help me to implement a semantic patch
Yes, of course.
> which allows to print out a warning before any pointer access,
This is possible in principle.
> if the pointer value not tested different from NULL.
Will it be more useful to look only at the value sources?
Did you inspect any examples?
Where do you get difficulties in your evolving SmPL scripts?
Regards,
Markus
next prev parent reply other threads:[~2015-05-09 7:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 9:00 [Cocci] Asking for help Zied Habtoul
2015-05-09 7:11 ` SF Markus Elfring [this message]
2015-05-09 10:31 ` [Cocci] Checking for null pointers Zied Habtoul
2015-05-09 11:01 ` SF Markus Elfring
2015-05-09 11:06 ` Zied Habtoul
2015-05-09 11:37 ` SF Markus Elfring
2015-05-09 11:48 ` Zied Habtoul
2015-05-09 12:01 ` SF Markus Elfring
2015-05-09 12:16 ` Zied Habtoul
2015-05-09 12:32 ` SF Markus Elfring
2015-05-09 12:39 ` Zied Habtoul
2015-05-09 13:00 ` SF Markus Elfring
2015-05-09 12:29 ` 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=554DB33D.2000000@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.