How do I create a bug report

This is an old revision of How do I create a bug report, edited by JuhaManninen at . The current revision is 27874.

/* What should be submitted via the Bug Tracker? */

This document contains some guidelines for using the FPC / Lazarus bug tracker as a reporter. This document is written for FPC / Lazarus users who identify bugs, have recommendations, want to submit patches or find other issues and want to report these to the Lazarus development team.

Code compilation errors

If you have errors when compiling code from latest SVN revision, please contact a proper FPC mailing list or Lazarus mailing list or better join #fpc or #lazarus-ide IRC channel on irc.freenode.net. Then the problem should be solved more promptly.

Check if the bug is not already reported

  1. Use the search field in View Issues. Hint: The searching is not smart: e.g. if you have a problem using TEdit.SelStart, search for "SelStart".

If the issue is already reported:

Note: you need to be logged in to perform these operations, see section #Logging/Creating new account.

Logging in / Creating new account

You need to be logged in to edit or submit 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.

What should be submitted via the Bug Tracker?

Please note: The Bug Tracker is not designed to field questions. These should be directed toward the Forums http://forum.lazarus.freepascal.org/.

Bug

The following page contains good tips about How to Report Bugs Effectively.

Regression bug caused by a certain revision

If you can find a revision in trunk that caused a bug, please report it. The report will usually be assigned to the author of that revision. You can find a quilty revision by a "bisect" process which is a binary search over the revisions. There are tools to help with that:

Suggestion

Explain your idea. A GUI mockup or an example of another tool using the feature can be helpful.

Improvement

Attachments

If you add source code or project sample attachments for the bug report (strongly recommended, see Tips on writing bug reports), please compress them using preferably these formats:

Other formats like 7zip, Bzip and RAR are ok, too. Nowadays tools for them are easily available.

Understanding the Report Status

An issue can have the following states:

See also