-
Notifications
You must be signed in to change notification settings - Fork 1
Reporting a Bug
Properly reporting a bug may reveal a mistake or misunderstanding on your part, which is a much faster fix than waiting for a Celeriac developer to help you. A bug report should include:
-
The program under investigation and the command line arguments used to run the program and Celeriac. The bug fixer needs the program in order to recreate the environment that caused the bug. An executable will suffice, however the source code is better if it's easy to build.
-
If you are reporting a bug with the .dtrace file, describe exactly what is wrong with the .dtrace file (i.e., what is there versus what you expected to see).
-
If possible, try to isolate the bug and submit submit only the relevant source code or executables required to reproduce the bug.
If you are fixing a bug for someone else, ask the person reporting the bug to make sure they have included this information.