cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Strace Labs <stracelabs@gmail.com>
Cc: cocci <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Changing format string usage with SmPL?
Date: Wed, 4 Dec 2019 07:47:43 +0100 (CET)	[thread overview]
Message-ID: <1624931283.11188831.1575442063589.JavaMail.zimbra@inria.fr> (raw)
In-Reply-To: <CABvP5W2+fUip+jEAO-G+ZyUPJhx5iCHcTRxkiYsiok_a3zTuRw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 4706 bytes --]

> De: "Strace Labs" <stracelabs@gmail.com>
> À: "Julia Lawall" <julia.lawall@inria.fr>
> Cc: "cocci" <cocci@systeme.lip6.fr>
> Envoyé: Mercredi 4 Décembre 2019 01:28:22
> Objet: Re: [Cocci] Changing format string usage with SmPL?

> Unfortunately, it doesn't work. But, I am working on some solutions using
> Python.

> therefore, once we have something like:

> ...
> @r1@
> format list fl;
> identifier fn;
> expression list e;
> position p;
> @@

> fn("%@fl@", e@p)
> ....

> Then, I could handle the format list using make_expr() as well. But, Is it
> possible to rename/handle the expression list?

Could you fix up the expression list first? Then you can write a rule like 

char[] s; 

fn(s, ..., 
- oldcode 
+ newcode 
,...) 

julia 

> On Tue, Dec 3, 2019 at 3:18 AM Julia Lawall < [ mailto:julia.lawall@inria.fr |
> julia.lawall@inria.fr ] > wrote:

>>> De: "Strace Labs" < [ mailto:stracelabs@gmail.com | stracelabs@gmail.com ] >
>>> À: "Markus Elfring" < [ mailto:Markus.Elfring@web.de | Markus.Elfring@web.de ] >
>>> Cc: "Julia Lawall" < [ mailto:julia.lawall@inria.fr | julia.lawall@inria.fr ] >,
>>> [ mailto:cocci@systeme.lip6.fr | cocci@systeme.lip6.fr ]
>>> Envoyé: Mardi 3 Décembre 2019 11:30:14
>>> Objet: Re: [Cocci] Changing format string usage with SmPL?

>>> On Sun, Dec 1, 2019 at 6:00 AM Markus Elfring < [ mailto:Markus.Elfring@web.de |
>>> Markus.Elfring@web.de ] > wrote:

>>>>> Basically, I intend to replace alls "%s" called with "mydata->name" by "%m" with
>>>> > "mydata" or "&mydata"

>>>> How far would you get the desired source code transformation based on
>>>> software extensions around a search pattern like the following.
>>>> ..........
>>>> Which algorithm will become sufficient for your data processing needs
>>>> around the usage of functions with variadic arguments because of format strings?

>>> Actually, I really didn't get why you're asking about that. because we are
>>> talking about X and you're asking for Y. but, either way. that is not the
>>> point. the point is because I am studying about the Coccinelle and I am just
>>> trying to figure out if the tool could detect "%s" called with "mydata->name"
>>> and then replace by "%m" and remove the "->name"

>>> e.g: Once if we have:

>>> int foo() {
>>> int id;
>>> struct mydata h1, *h2, s1, *s2;
>>> char *city = "Hello";
>>> my_printf("%s", s2->name);
>>> my_printf("hi hi %s gggg", [ http://h1.name/ | h1.name ] );
>>> my_printf("1234 %d %s @ %d %s | %s -> city=%s", id, [ http://s1.name/ | s1.name
>>> ] , 12, (*h2).name , h2->name , city);
>>> my_printf("aaaa %s hhhhh", h2->name);
>>> my_printf("%s", city);
>>> }

>>> Then, replace by:

>>> int foo() {
>>> int id;
>>> struct mydata h1, *h2, s1, *s2;
>>> char *city = "Hello";
>>> my_printf("%m", s2);
>>> my_printf("hi hi %s gggg", &h1);
>>> my_printf("1234 %d %m @ %d %m | %m -> city=%s", id, [ http://s1.name/ | s1.name
>>> ] , 12, (*h2).name , h2->name , city);
>>> my_printf("aaaa %s hhhhh", h2);
>>> my_printf("%s", city);
>>> }

>>> But, I've read again the other samples and the documentation. therefore, I
>>> didn't figure out how it should be. btw, thank you Julia for the suggestion
>>> performing the Ocalm/make_expr/replace . (Due to something wrong with the
>>> Coccinelle distributed by Brew/Osx. I just rewrote your sample using Python and
>>> the result was the same. But, I can't just replace all "%s" by "%m". As I said,
>>> it should be only if the "%s" was declared to use "mydata->name".

>>> so, I still fighting yet. thanks in Advance.

>> OK, if you may have more than one argument to your print, then you can find the
>> offset using an expression list metavariable:

>> @r@
>> expression list[n] between;
>> @@

>> print(s,between,h2->name,...)

>> Then you can use r.n in your python rule to figure out where is the %s to
>> change. Unfortunately, this will not work well if there are multiple name
>> references in the argument list. Because you will be trying to change the
>> format string in multiple ways, eg once where between has length 2 and once
>> where between has length 4. Substantial hacks would be required to deal with
>> this.

>> It would be nice if you could do

>> @r@
>> expression list[bn] between;
>> expression list[an] after;
>> position p;
>> @@
>> print@p(s,between,name,after)

>> @@
>> format list[ [ http://r.bn/ | r.bn ] ] f1;
>> format list[ [ http://r.an/ | r.an ] ] f2;
>> position r.p;
>> @@
>> print@p(
>> - "%@f1@%s%@f2@"
>> + "%@f1@%m%@f2@"
>> , l)

>> I don't know if that would work, though.

>> julia

>>>> Regards,
>>>> Markus

[-- Attachment #1.2: Type: text/html, Size: 8688 bytes --]

[-- Attachment #2: Type: text/plain, Size: 136 bytes --]

_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  parent reply	other threads:[~2019-12-04  6:49 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28  2:11 [Cocci] Replacing printf/format calls based on the data-type Strace Labs
2019-11-28  7:07 ` Julia Lawall
2019-11-28 17:45   ` Strace Labs
2019-11-29 14:48   ` [Cocci] Replacing printf() parameters according to used data types Markus Elfring
2019-11-28  7:50 ` Markus Elfring
2019-11-29  0:35   ` Jorge Pereira
2019-11-29  8:29     ` Markus Elfring
2019-11-29 10:57       ` Strace Labs
2019-11-29 12:33         ` Markus Elfring
2019-11-29 14:47           ` Strace Labs
2019-11-29 16:08             ` Markus Elfring
2019-11-29 17:19               ` Strace Labs
2019-11-29 17:45                 ` Markus Elfring
2019-11-29 20:55             ` Julia Lawall
2019-11-30  2:25               ` Strace Labs
2019-11-30  6:35                 ` Julia Lawall
2019-11-30  8:46                 ` Markus Elfring
2019-12-01  8:00                 ` [Cocci] Changing format string usage with SmPL? Markus Elfring
2019-12-03  3:30                   ` Strace Labs
2019-12-03  5:18                     ` Julia Lawall
2019-12-03 13:28                       ` Markus Elfring
2019-12-03 15:43                       ` [Cocci] Generation of expression lists by SmPL script rules? Markus Elfring
2019-12-03 17:28                       ` [Cocci] Changing format string usage with SmPL? Strace Labs
2019-12-04  0:21                         ` Strace Labs
2019-12-06 19:36                           ` Markus Elfring
2019-12-07  7:49                           ` Markus Elfring
2019-12-04  6:47                         ` Julia Lawall [this message]
2019-12-06 19:44                           ` Markus Elfring
2019-12-06 19:20                         ` Markus Elfring
2019-12-03 10:01                     ` Markus Elfring
2019-11-30 15:11               ` [Cocci] Replacing printf() parameters according to used data types 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=1624931283.11188831.1575442063589.JavaMail.zimbra@inria.fr \
    --to=julia.lawall@inria.fr \
    --cc=cocci@systeme.lip6.fr \
    --cc=stracelabs@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).