Using the Bug Tracking System
You must have an account to report an issue on the Bug Tracking System (BTS)
. If you are creating your account for your first bug report, consider this trade-off carefully: we will never use your e-mail address to contact you for something other than the bug you reported. But if you provide an invalid e-mail address, your bug may linger for months because the assignee is waiting for more feedback and you didn't receive the notice.
Whenever possible, include HOW TO REPRODUCE
the issue. Provide everything necessary for a smart, but not mind-reading, human to reproduce the bug: input files, command line used, sequence of actions. If your analysis project depends on system headers, please use one of the two options from this message
If possible, attach the automatically-generated journal (by default called
). Journals are enabled automatically when you use the GUI
, or when using option
. Including a journal or a backtrace when available does not exempt you from providing the input files: a backtrace or a journal alone do not contain enough information to reproduce the behavior.
Include the CATEGORY
, that is which part of Frama-C is concerned by your bug report or feature request. Note that issues related to Why, including issues with Why's Graphical User Interface, must be classified in the category “Plug-in > Jessie” (and not in the category “Graphical User Interface” which is only relevant for issues specific to Frama-c's GUI
mantis/frama-c/bug_reporting_guidelines.txt · Last modified: 2014/05/29 10:59 by yakobowski