|
|
|
- Use English to report an issue on the BTS. Using French is also acceptable to report a _private_ issue.
|
|
|
|
|
|
|
|
- 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](https://lists.gforge.inria.fr/pipermail/frama-c-discuss/2008-December/000831.html).
|
|
|
|
|
|
|
|
- If possible, attach the automatically-generated journal (by default called `frama_c_journal.ml`). Journals are enabled automatically when you use the GUI, or when using option `-journal-enable`. 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 _OBTAINED BEHAVIOR_ in enough detail that someone else (smart, but not mind-reading) can decide if they have reproduced your bug.
|
|
|
|
|
|
|
|
- Include the _CATEGORY,_ that is which part of Frama-C is concerned by your bug report or feature request.
|
|
|
|
|
|
|
|
- If the bug report is not for a crash, include the EXPECTED BEHAVIOR that you would have liked to see. |