Frama-C Bug Tracking System

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000508Frama-CGraphical User Interfacepublic2010-06-14 08:172011-01-28 12:22
Assigned Tosignoles 
StatusclosedResolutionunable to reproduce 
PlatformOSOS Version
Product VersionFrama-C Boron-20100401 
Target VersionFixed in Version 
Summary0000508: An erorr appears when executing right-click on the source-file name(left side of the screen).
DescriptionThe full backtrace is: Raised at file "src/pdg_types/", line 548, characters 22-25 Called from file "src/pdg_types/", line 554, characters 32-48 Called from file "src/security_slicing/", line 393, characters 2-80 Called from file "", line 74, characters 24-34 Called from file "", line 74, characters 24-34 Called from file "src/security_slicing/", line 601, characters 22-53 Called from file "src/security_slicing/", line 676, characters 14-69 Called from file "src/lib/", line 746, characters 40-45 Called from file "src/kernel/", line 323, characters 15-26 Re-raised at file "src/kernel/", line 338, characters 14-15 Called from file "src/impact/", line 117, characters 15-37 Called from file "src/lib/", line 176, characters 12-15 Re-raised at file "src/lib/", line 181, characters 10-11 Called from file "src/gui/", line 533, characters 8-385 Unexpected error (PdgTypes.Pdg.Top). Please report as 'crash' at
TagsNo tags attached.
Attached Filesc file icon main.c [^] (199 bytes) 2010-06-14 09:34 [Show Content]
jpg file icon error 2.JPG [^] (185,651 bytes) 2010-06-14 11:10

- Relationships
related to 0000517closedmonate Exception raised if dot not found 

-  Notes
signoles (manager)
2010-06-14 08:59

Please could you provide an easy way (C files, command line, etc) to reproduce your issue?
signoles (manager)
2010-06-14 10:04

Thanks for the attached file. However I'm still unable to reproduce your issue. If I run "frama-c-gui main.c", then I right-click on "main.c" in the filetree, that's only printed the code without error. By the way, right clicking on the source-file name never computes the PDG nor the security slicing as the backtrace shows. So what actions do you exactly do? Could you also provide the generated file
adytzul_ac (reporter)
2010-06-14 10:58 has 0 bytes (it's empty).
signoles (manager)
2010-06-14 11:00

OK. But: 1) What is your command line? 2) What actions do your perform step by step in the GUI?
adytzul_ac (reporter)
2010-06-14 11:09

These are my first days using this tool so I did not give to much attention to the command line window. It would have been a good idea to make a screen capture of this window. Before the error appeared, I was performing a Value Analisys and browsing the messages that resulted from this analysis. At a moment, I performed a right click inside the file view area and the error appeared. Now, after the following steps, a similar error appeared: - performing Value Analysis - selecting Impact Analysis Output: see JPEG from the attachement
signoles (manager)
2010-06-14 13:42

I perform an impact analysis on each statement of your program, after performing value analysis generating the very same alarms that the ones you have. I'm still unable to reproduce your issue. Thanks to the initial provided backtrace, I could strengthen the code raising the exception but being able to reproduce the error would be very helpful: writing code without being able to test it is not the usual way to fix a bug... Besides: 1) actually it should be not possible that has 0 byte after exiting Frama-C. Either it does not exist, or it contains something (at least, the date of generation and some constant stuff). 2) the error in the DOS console is independent of the backtrace in the dialog box. It indicates that you haven't `dot' ( installed on your system. `dot' is required by Frama-C for displaying graphs. We should provide a better error message instead of an uncaught exception
signoles (manager)
2010-06-22 10:56

See BTS #517 for the error about `dot'.
signoles (manager)
2011-01-28 12:22

1) Try to fix this bug but unable to reproduce the initial issue. 2) An error remains. See bts #517.

- Issue History
Date Modified Username Field Change
2010-06-14 08:17 adytzul_ac New Issue
2010-06-14 08:17 adytzul_ac Status new => assigned
2010-06-14 08:17 adytzul_ac Assigned To => monate
2010-06-14 08:59 signoles Note Added: 0000930
2010-06-14 08:59 signoles Assigned To monate => signoles
2010-06-14 08:59 signoles Status assigned => feedback
2010-06-14 09:34 adytzul_ac File Added: main.c
2010-06-14 10:04 signoles Note Added: 0000931
2010-06-14 10:58 adytzul_ac Note Added: 0000932
2010-06-14 11:00 signoles Note Added: 0000933
2010-06-14 11:09 adytzul_ac Note Added: 0000934
2010-06-14 11:10 adytzul_ac File Added: error 2.JPG
2010-06-14 13:42 signoles Note Added: 0000935
2010-06-22 10:52 signoles Status feedback => acknowledged
2010-06-22 10:55 signoles Relationship added related to 0000517
2010-06-22 10:56 signoles Note Added: 0000944
2011-01-28 12:22 signoles Note Added: 0001432
2011-01-28 12:22 signoles Status acknowledged => closed
2011-01-28 12:22 signoles Resolution open => unable to reproduce

Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker