User Tools

  • Logged in as: anonymous (anonymous)
  • Logout

Site Tools


mantis:frama-c:bug_reporting_guidelines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

mantis:frama-c:bug_reporting_guidelines [2014/05/29 10:55]
yakobowski Correct name for -journal-enable
mantis:frama-c:bug_reporting_guidelines [2014/05/29 10:59] (current)
yakobowski English
Line 6: Line 6:
   * 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 [[http://​lists.gforge.inria.fr/​pipermail/​frama-c-discuss/​2008-December/​000831.html|this message]].   * 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 [[http://​lists.gforge.inria.fr/​pipermail/​frama-c-discuss/​2008-December/​000831.html|this message]].
  
-  *  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 dispense ​from providing the input files: ​alone, ​a backtrace or journal do not contain enough information to reproduce the behavior.+  *  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 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 **OBTAINED BEHAVIOR** in enough detail that someone else (smart, but not mind-reading) can decide if they have reproduced your bug.
mantis/frama-c/bug_reporting_guidelines.txt ยท Last modified: 2014/05/29 10:59 by yakobowski