Submission guidelines¶

Submit a bug¶

If you have encountered a bug during running DFF, give some feedbacks by registering on the tracker. Your registration will be validated and you will be able to report bugs.

In order to let the team react rapidly, you will have to provide some information:

• Architecture (x86 / amd64, ...)
• Operating System (Windows, Linux, Unix, ...), its version and finally if 32 or 64 bits
• The complete traceback

Category of bugs¶

• If DFF provides the traceback through the python interpreter, then copy and paste it.
• If DFF segfaults (yes, it could be possible...), you have several ways to give us some useful details

Segfault tracking under Linux / Unix:¶

• if it segfaults at start:

user@dff > ulimit -c 2000000
user@dff > ./dff.py
user@dff > gdb -c core

• if it segfault during the use:

1) run dff.py
2) type the following command in another terminal

user@dff > pgrep dff
user@dff > 3442
user@dff > gdb
(gdb) attach 3442
[...]
(gdb) c

3) Try to generate the encountered segfault and then go back to gdb and type:

(gdb) bt
[...]

• In the bug request, provide results provided by gdb.

Segfault tracking under Windows¶

In order to track segfault under Windows, you will need to run the project through Visual Studio. It will provide some details concerning the segfault.

Features requests¶

If you need or want some specific features, either you can post your request on the dedicated discussions of forums or report it via the tracker by tagging with "features".