Ptanal polishing #13
Ptanal polishing #13
Conversation
To use the Points-to-analysis module (Ptranal) it is not only
necessary to call Ptranal.analyze_file as stated in the documentation,
but to run Ptranal.compute_results afterwards and in particular before
any call to the "database query" functions of the module.
This fixes the initial problem as reported in issue #141 ("Bug in
pointer analysis or documentation")
http://sourceforge.net/p/cil/bugs/141/
This partly fixes issue #146 ("Olf vs. Golf in Ptranal")
http://sourceforge.net/p/cil/bugs/146/
|
Thanks @cspiel. This is a good starting point. I'll tweak your patches and merge them. Comments:
As a matter of fact, the ptanal-fixes branches has added such a functionality. I will amend the doc accordingly.
This option should not be documented (and it is, in fact, not exposed), because it does not switch the backend. More precisely, for ugly technical reasons related to typing, the choice of backend must be done when the module is loaded: the only available information at that point is the command-line, which is parsed, setting this reference, and then making tricks with first class modules to load the right one. Changing the reference later does not affect which module is used. |
|
@kerneis, I did not know that the "multi-entry" feature of Ptranal So, please kick out my scribbling about |
@kerneis: as promised - documentation updates