Difference between revisions of "How do I create a bug report"
From Free Pascal wiki
Jump to navigationJump to search (→Enter the bug in the Lazarus Bug Tracker: fixed links to the bug tracker) |
|||
| Line 4: | Line 4: | ||
== Enter the bug in the Lazarus Bug Tracker == | == Enter the bug in the Lazarus Bug Tracker == | ||
| − | * Go to the [http:// | + | * Go to the [http://bugs.freepascal.org/mantis/set_project.php?project_id=1 Lazarus bug tracker] |
| − | * You need to be logged in to make bug reports. If you are logged in as guest, you need to log out first (Guests cannot make reports, only watch them). If you already have an account go to the [http:// | + | * You need to be logged in to make bug reports. If you are logged in as guest, you need to log out first (Guests cannot make reports, only watch them). If you already have an account go to the [http://bugs.freepascal.org/mantis/login_page.php login page], otherwise create a new account on the [http://bugs.freepascal.org/mantis/signup_page.php sign up page]. |
| − | * After having logged in go to the [http:// | + | * After having logged in go to the [http://bugs.freepascal.org/mantis/bug_report_advanced_page.php Report Issue] page. Fill in as much as you can and know. The more specific, the better. |
* Important fields are the OS and Product fields and the steps to reproduce this issue. If an issue cannot be reproduced by the developers, they cannot start to fix it. | * Important fields are the OS and Product fields and the steps to reproduce this issue. If an issue cannot be reproduced by the developers, they cannot start to fix it. | ||
* It is often useful to upload a small test application that shows the bug, and this speeds up correcting it. | * It is often useful to upload a small test application that shows the bug, and this speeds up correcting it. | ||
* If there is some graphical error, it is useful to upload a (partial) screenshot (in png or jpeg, not bmp format). | * If there is some graphical error, it is useful to upload a (partial) screenshot (in png or jpeg, not bmp format). | ||
* If it is a crash, try to create a backtrace. See [[Creating a Backtrace with GDB]] for more info. | * If it is a crash, try to create a backtrace. See [[Creating a Backtrace with GDB]] for more info. | ||
Revision as of 10:33, 27 December 2007
│ Afrikaans (af) │
Deutsch (de) │
English (en) │
français (fr) │
português (pt) │
русский (ru) │
You found a bug in Lazarus and you want to report it to the developers. This page tells you how to do that.
Enter the bug in the Lazarus Bug Tracker
- Go to the Lazarus bug tracker
- You need to be logged in to make bug reports. If you are logged in as guest, you need to log out first (Guests cannot make reports, only watch them). If you already have an account go to the login page, otherwise create a new account on the sign up page.
- After having logged in go to the Report Issue page. Fill in as much as you can and know. The more specific, the better.
- Important fields are the OS and Product fields and the steps to reproduce this issue. If an issue cannot be reproduced by the developers, they cannot start to fix it.
- It is often useful to upload a small test application that shows the bug, and this speeds up correcting it.
- If there is some graphical error, it is useful to upload a (partial) screenshot (in png or jpeg, not bmp format).
- If it is a crash, try to create a backtrace. See Creating a Backtrace with GDB for more info.
