From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Checking for null pointers
Date: Sat, 09 May 2015 14:32:15 +0200 [thread overview]
Message-ID: <554DFE4F.1050901@users.sourceforge.net> (raw)
In-Reply-To: <CABBGRWv9UiJ0WBdPVC=Uj_osqgzhwoOrT3uTqFCzSjVe3T1QmA@mail.gmail.com>
> ?, i want that my scripts detects only the access to pointer
> and not its declaration, cast or initialization.
Will it be more useful to find the source code places
where a null pointer occurs (before an access try will happen)?
How do you think about more fine-tuning for your SmPL scripts?
Would you like to extend my previous approaches for
return value checking?
Regards,
Markus
next prev parent reply other threads:[~2015-05-09 12:32 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 ` [Cocci] Checking for null pointers SF Markus Elfring
2015-05-09 10:31 ` 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 [this message]
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=554DFE4F.1050901@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.