Julia: > @initialize:python@ > @@ > > print "hello" > > @@ > @@ > > - of_node_put(...);
This is now fixed: the initialization code was executed once, but the output was not flushed before the fork, leading the buffered output to be duplicated among all the child processes. Thanks for reporting this. -- Thierry. Julia Lawall (2016/12/19, 06:54 UTC) : > On Sun, 18 Dec 2016, SF Markus Elfring wrote: > >> >> Can you generally clarify current consequences from usage of a SmPL rule >> >> “initialize:…” >> >> together with the parameter “--jobs” for the program “spatch”? >> > >> > It should happen only once. >> >> Thanks for this information. >> >> I would like to know if the script initialisation should happen for each >> background process and/or after the start of the program “spatch”. >> >> >> > Thus without your semantic patch and your .c file, I can't tell >> > why it doesn't behave as expected. >> >> You got the corresponding data from my source code analysis try for NetBSD. >> How often do you observe a simple text line output from initialisation code >> after parallel execution of one from your test scripts? > > It seems to be a problem with python initialization only. Here is my > example script: > > @initialize:python@ > @@ > > print "hello" > > @@ > @@ > > - of_node_put(...); > > Note how few lines it contains, how it is designed to illustrate the > specific problem, how easy it is to adapt to any software project one has > handy, how it is included in the email for easy reference etc. Please do > the same. > > julia_______________________________________________ > Cocci mailing list > [email protected] > https://systeme.lip6.fr/mailman/listinfo/cocci _______________________________________________ Cocci mailing list [email protected] https://systeme.lip6.fr/mailman/listinfo/cocci
