BugTracker

The bug reports are vital for VLE to obtain the strongest application. It is very important for us that the stable versions of VLE are the most stable possible that is, without crash, without minor bug and without translation error. So, if you discover a bug in the VLE project, do not hesitate to warn developers.

Bugs Reporting
The bug reports are to be made in our bug tracker. Before being able to add reports, it will be necessary to register you as user on the Sourceforge site. The VLE project proposes several tracker, three first ones concern the VLE project generally if you do not know where to post. Three last ones concern parts of the project VLE.
 * Bugs : to report VLE bugs
 * Part: gvle (fr) : management of the graphical user interface
 * Part: pyvle (fr) : management of the python version of VLE
 * Part: rvle (fr) : management of the R package
 * Part: vle-web (fr) : management of the web-site based on pyvle

Building a bug report
The more precise is your bug report, the more it will be simple to reproduce and to fix. If you are using Linux, install the Gdb program which must be packaged on your Linux distribution and type the following commands:

$ gdb --args vle [parameters] (gdb) catch throw (gdb) run ... signaled error (gdb) bt or bt full ... stack of calls ...

To debug from the main function of VLE: $ gdb --args vle [paramètres] (gdb) catch throw (gdb) break main # to add a breakpoint from the main function (gdb) break 'vle::RootCoordinator::run' # to add a breakpoint on the main loop simulation function (gdb) next / step (gdb) bt or bt full ... stack of calls ...

To report a bug, please copy out this stack of calls in your e-mail. If it is an error in GVLE, EOV, replace the name of the program in the command-line provided as argument to Gdb.