Frama-C Bug Tracking System

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002276Frama-CGraphical User Interfacepublic2017-02-03 09:282017-11-27 10:25
ReporterMax P. 
Assigned Tomaroneze 
PrioritynormalSeveritytweakReproducibilityalways
StatusacknowledgedResolutionreopened 
PlatformOSOS Version
Product VersionFrama-C 14-Silicon 
Target VersionFixed in Version 
Summary0002276: Duplicates are created on the tab "Messages"
DescriptionNew messages append to old messages on the tab "Messages" if an analysis are rerun with new options.
Steps To Reproduce1. Run Value analysis. 2. Change any option. 3. Run Value analysis.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0006352)
maroneze (developer)
2017-02-03 13:43

This is intentional, although it might be considered counter-intuitive. Running subsequent analyses in the GUI is equivalent to using command-line option `-then`, which exhibits the same behavior as you described. This behavior makes more sense when running different plug-ins (e.g. derived Value plug-ins such as Nonterm), each of them emitting different messages. It also makes sense for other plug-ins such as WP, which are modular, and therefore likely to be executed several times in sequence. For a whole-program analysis such as Value, this makes little sense. The recommended approach when using Value is to parse and parameterize it using the command-line, and then use the GUI mainly to inspect results (falling back to the command-line for further parameterization).
(0006354)
Max P. (reporter)
2017-02-03 16:51
edited on: 2017-02-06 08:34

Maybe you should add a button "Clear messages"? Even better would be to check whether there is such a record and do not add a duplicate. It is not always possible to achieve the desired at a time. See https://bts.frama-c.com/view.php?id=2277
(0006474)
maroneze (developer)
2017-11-27 10:25

The logging mechanism in the GUI is due to be revamped in a future release and the new behavior will likely prevent this situation from happening.

- Issue History
Date Modified Username Field Change
2017-02-03 09:28 Max P. New Issue
2017-02-03 09:28 Max P. Status new => assigned
2017-02-03 09:28 Max P. Assigned To => maroneze
2017-02-03 13:43 maroneze Note Added: 0006352
2017-02-03 13:43 maroneze Status assigned => closed
2017-02-03 13:43 maroneze Resolution open => won't fix
2017-02-03 16:51 Max P. Note Added: 0006354
2017-02-03 16:51 Max P. Status closed => feedback
2017-02-03 16:51 Max P. Resolution won't fix => reopened
2017-02-03 17:12 Max P. Note Edited: 0006354 View Revisions
2017-02-06 08:34 Max P. Note Edited: 0006354 View Revisions
2017-11-27 10:25 maroneze Note Added: 0006474
2017-11-27 10:25 maroneze Status feedback => acknowledged


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker