Sign in Join
Wiki copytemporary

How do I create a bug report/ja: what changed

Revision 0 to 1. Removed lines have a minus sign; added lines have a plus sign.

Title: How do I create a bug report/ja

OldNewLine
1+**日本語版メニュー**
2+---
3+[[Main Page/ja|メインページ]] \- [[Lazarus Documentation/ja|Lazarus Documentation日本語版]] \- [[Japanese Localization Notes|翻訳ノート]] \- [[Bug Tracking/ja|日本語障害情報]]
4+
5+
6+You found a bug in Lazarus and you want to report it to the developers. This page tells you how to do that.
7+
8+## Lazarus code compilation errors
9+
10+If you have errors when compiling code from latest SVN revision, please contact the [Mailing list](<http://www.lazarus.freepascal.org/modules.php?op=modload&name=StaticPage&file=index&sURL=maill>) or better join #lazarus-ide IRC channel on irc.freenode.net. Then the problem should be solved more promptly.
11+
12+## Check if the bug is not already reported
13+
14+ 1. Use search field in [View Issues](<http://bugs.freepascal.org/view_all_set.php?type=3&source_query_id=1482>). Hint: The searching is quite dummy, if you e.g. have problem with using TEdit.SelStart, try to search for "SelStart".
15+
16+If the same issue is already reported:
17+
18+ * reopen it, if the bug report has been resolved or closed - use Reopen Issue button
19+ * add a note, if you have reproduce this bug in different situation than reported
20+ * you can set to monitor changes in this bug report - use Monitor Issue button
21+
22+Note: you need to be logged to perform these operations, see section #Logging/Creating new account.
23+
24+## Enter the bug in the Lazarus Bug Tracker
25+
26+ 1. Go to the [Lazarus bug tracker](<http://bugs.freepascal.org/set_project.php?project_id=1>)
27+ 2. You need to be logged, see section #Logging/Creating new account
28+ 3. Go to the [Report Issue](<http://bugs.freepascal.org/bug_report_advanced_page.php>) page. Fill in as much as you can and know. The more specific, the better.
29+ * 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! Do not forget to mention, if you are using some exotic PC architecture (big endian or 64-bit).
30+ * It is often useful to upload a small test application that shows the bug, and this speeds up correcting it.
31+ * If there is some graphical error, it is useful to upload a (partial) screenshot (in png or jpeg, not bmp format).
32+ * If it is a crash, try to create a backtrace. See [[Creating a Backtrace with GDB]] for more info.
33+ * You can try to reproduce the bug on as many different platforms as you can - it helps to determinate if it is widget specific issue.
34+ * You can boost fixing the bug by submitting a bounty, see [[Bounties]].
35+
36+
37+
38+## Logging/Creating new account
39+
40+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](<http://bugs.freepascal.org/login_page.php>), otherwise create a new account on the [sign up page](<http://bugs.freepascal.org/signup_page.php>).
41+
42+---
43+*From the Free Pascal wiki, page "How do I create a bug report/ja", as the Internet Archive kept it on 2020-08-14, last changed on 2011-08-03. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).*

Back to history