Collect values not only at function enter/exit

[Andrea Fioraldi]

Hi to all,

I'm new to Daikon and I'm considering to use it as a part of my master thesis.

I'm going to write a frontend for C and C++ (with LLVM 10, maybe looking at https://github.com/markus-kusano/udon) that focus only on class/structs invariants.

I want also to dump the value of variables not simply on functions enter and exit, but more frequently at every access to the monitored variable.

As a total noob in this field, I have difficulties in evaluating the feasibility of this part of my project.

Can you help me? Do you think that Daikon is the right tool for this?

Thank you all,

Andrea

[Michael Ernst]

What you propose should work fine.  The front end can make any choices about where to obtain data.

Daikon is agnostic to where its data comes from (function entry and exit, or other program points, or even data that does not come from running a program).

Mike

--
You received this message because you are subscribed to the Google Groups "Daikon discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to daikon-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/daikon-discuss/d42a52de-5e51-4cdf-8367-829c317adf98%40googlegroups.com.

[Andrea Fioraldi]

Thank you Micheal for the answer.

This means that the ppt is simply a label?

If I generate for instance

ppt ..FOOBAR123
  ppt-type enter
  variable ::words2
    var-kind variable
    rep-type hashcode
    dec-type char**
    comparability 1

Instead of (from kvasir):

ppt ..main():::ENTER
  ppt-type enter
  variable ::words2
    var-kind variable
    rep-type hashcode
    dec-type char**
    comparability 1

It will works fine?

Ofc I have to maintain the consistence between the ppr labels in the decls and the dtrace.

Regards,

Andrea

Il giorno giovedì 19 marzo 2020 21:38:59 UTC+1, Michael Ernst ha scritto:

What you propose should work fine.  The front end can make any choices about where to obtain data.

Daikon is agnostic to where its data comes from (function entry and exit, or other program points, or even data that does not come from running a program).

Mike

On Thu, Mar 19, 2020 at 1:36 PM Andrea Fioraldi <andreaf...@gmail.com> wrote:

Hi to all,

I'm new to Daikon and I'm considering to use it as a part of my master thesis.

I'm going to write a frontend for C and C++ (with LLVM 10, maybe looking at https://github.com/markus-kusano/udon) that focus only on class/structs invariants.

I want also to dump the value of variables not simply on functions enter and exit, but more frequently at every access to the monitored variable.

As a total noob in this field, I have difficulties in evaluating the feasibility of this part of my project.

Can you help me? Do you think that Daikon is the right tool for this?

Thank you all,

Andrea

--
You received this message because you are subscribed to the Google Groups "Daikon discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to daikon-...@googlegroups.com.

[Michael Ernst]

Andrea-

Yes, the ppt name is just a label.  You can choose any name you like.

The file formats are described at http://plse.cs.washington.edu/daikon/download/doc/developer.html#File-formats .

Mike

To unsubscribe from this group and stop receiving emails from it, send an email to daikon-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/daikon-discuss/ef2ddb72-d4e9-4d43-9d1d-32376f9e5e62%40googlegroups.com.