From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] array index range checking
Date: Thu, 21 May 2015 23:13:53 +0200 [thread overview]
Message-ID: <555E4A91.2010300@users.sourceforge.net> (raw)
In-Reply-To: <CABBGRWtAHM7naeENzeVQu_n0QC9EhCpUEvv_0MyZ+VH8zfxgxg@mail.gmail.com>
> the script must detect an error on ( T[20] = 5 ;)
> because there is an overflow of the array size.
Did you experiment with any SmPL script already?
> any suggestions please to implement this script ?
Would you like to analyse affected source code
only with constant array indexes?
Do you need to check for inappropriate numbers with
a bit of additional Python or OCaml programming?
Regards,
Markus
next prev parent reply other threads:[~2015-05-21 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 10:19 [Cocci] array addressing range checking by coccinelle Zied Habtoul
2015-05-21 21:13 ` SF Markus Elfring [this message]
2015-05-21 21:55 ` [Cocci] array index range checking Zied Habtoul
2015-05-22 5:47 ` SF Markus Elfring
2015-05-22 8:59 ` Zied Habtoul
2015-05-22 10:05 ` SF Markus Elfring
2015-05-22 10:13 ` Zied Habtoul
2015-05-22 10:40 ` SF Markus Elfring
2015-05-22 11:11 ` Julia Lawall
2015-05-22 11:53 ` SF Markus Elfring
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=555E4A91.2010300@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox