{"id":101737,"date":"2021-10-24T22:22:41","date_gmt":"2021-10-24T20:22:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/intel-otkryl-kod-sistemy-mashinnogo-obucheniya-controlflag-dlya-vyyavleniya-oshibok-v-kode"},"modified":"2021-10-24T22:22:41","modified_gmt":"2021-10-24T20:22:41","slug":"intel-otkryl-kod-sistemy-mashinnogo-obucheniya-controlflag-dlya-vyyavleniya-oshibok-v-kode","status":"publish","type":"post","link":"https:\/\/prohoster.info\/da\/blog\/news\/intel-otkryl-kod-sistemy-mashinnogo-obucheniya-controlflag-dlya-vyyavleniya-oshibok-v-kode","title":{"rendered":"Intel har frigivet koden til kontrolsystemet ControlFlag for maskinl\u00e6ring til fejlfinding i koden.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Intel har \u00e5bnet deres arbejde relateret til forskningsprojektet ControlFlag, som sigter mod at skabe et maskinl\u00e6ringssystem til at forbedre kodekvaliteten. Det v\u00e6rkt\u00f8j, der er udviklet af projektet, g\u00f8r det muligt at identificere forskellige fejl og anomalier i kildekoden, skrevet i h\u00f8jniveau programmeringssprog som C\/C++, baseret p\u00e5 en model, der er tr\u00e6net p\u00e5 en stor m\u00e6ngde eksisterende kode. Systemet er velegnet til at identificere forskellige typer problemer i koden, fra at finde typografiske fejl og forkerte typekombinationer til at opdage manglende NULL-v\u00e6rdi kontrol i pegepinde og problemer med hukommelse. ControlFlag-koden er skrevet i C++ og frigivet under MIT-licensen. <\/p>\n
Systemet l\u00e6rer selv ved at opbygge en statistisk model af det eksisterende kodeudsnit fra \u00e5bne projekter, der er offentliggjort p\u00e5 GitHub og lignende offentlige repositoryer. Under tr\u00e6ningsfasen identificerer systemet typiske m\u00f8nstre i kodens konstruktioner og bygger et syntaktisk tr\u00e6, der viser forbindelserne mellem disse m\u00f8nstre og afspejler kodens udf\u00f8relsesflow i programmet. Som resultat dannes et referencebeslutningstr\u00e6, der integrerer udviklingserfaringen fra alle analyserede kildefiler. <\/p>\n
For the checked code, a similar process is implemented to identify patterns that are compared with the reference decision tree. Significant discrepancies with neighboring branches indicate anomalies in the checked pattern. The system also not only identifies errors in the pattern but also suggests corrections. For instance, in the OpenSSL code, the construct (s1 == NULL) \u2227 (s2 == NULL) was found in the syntax tree only 8 times, whereas the nearest branch with the value (s1 == NULL) || (s2 == NULL) appeared around 7 thousand times. The system also detected the anomaly (s1 == NULL) | (s2 == NULL), which appeared in the tree 32 times.
<\/center> <\/p>\n
When analyzing the code fragment if (x = 7) y = x; the system determined that typically, the operator if uses the construct variable == number for comparing numeric values, so the indication variable = number in the if expression is likely due to a typographical error. Traditional static analyzers would catch such an error, but unlike them, ControlFlag does not apply preset rules that struggle to account for all possible variations, but rather relies on the statistics of usage of various constructs across numerous projects. <\/p>\n
As an experiment, using ControlFlag, unnoticed errors in the cURL utility's source texts, which is often cited as an example of quality and verified code, were identified by static analyzers when using the structure element s->keepon, which had a numeric type but was compared with a boolean value TRUE. In the OpenSSL code, in addition to the previously mentioned issue with (s1 == NULL) \u2227 (s2 == NULL), anomalies were also identified in the expressions (-2 == rv) (the minus was a typographical error) and BIO_puts(bp, ':') \n Kilde: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
![\"Intel](\"\/wp-content\/uploads\/2021\/10\/f59e59e606a113aac675d44fd97845bd.jpg\")
<\/center> <\/p>\n