Reporting Boost bugs
- If you know where to look in the source code, make sure the bug isn't already fixed in the latest sources. The most recent version of everything on the Boost web site is available from the git repositories.
- Search the bug database to make sure we don't already know about the bug. If we do, you can add further information to an existing bug ticket.
- If you have a userid on the Boost Trac server, please log in.
- Even if you don't have a userid, visit the preferences page to enter or confirm an email address at which you can be reached. Most bug reports require some interaction with the reporter, and if we can't follow up with you, chances are good that your efforts at reporting the bug will be wasted.
-
Create a new ticket in the bug tracker.
If possible,
- Fill out all the fields completely, especially the “component” field that identifies the library. That will help ensure your report is noticed by the appropriate developers.
- Attach a minimal and complete program that reproduces the problem. Aside from helping the library maintainer fix the problem, you may find the bug in your own code, which can avoid a costly delay waiting for a response.
If You Have a Fix for the Bug
After completing the steps above, please submit a patch or a pull request as described in the wiki.
