Sign in Join
Wiki copytemporary

error messages: what changed

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

Title: error messages

OldNewLine
1+## Errors during compilation
2+
3+Unless the error identifies itself as an internal compiler error, it is unlikely that the error is caused by a bug in the compiler or its runtime library. Syntax errors are almost always due to incorrect code. Refer to the FPC [Parser Messages](https://www.freepascal.org/docs-html/user/userse62.html) documentation for a listing of the various Error and Warning messages produced by the FPC Parser along with explanations of them.
4+
5+If you encounter an error while compiling your code and are unable to resolve it yourself, please use the FPC and Lazarus [Forums](https://forum.lazarus.freepascal.org/), write to the [Lazarus](https://lists.lazarus-ide.org/listinfo/lazarus) or [Free Pascal](https://www.freepascal.org/maillist.html) mailing list. The problem may then be solved more quickly.
6+
7+If an error is encountered during compilation, the compiler does not generate an executable program. See further [[compile-time error|compile time errors]].
8+
9+## Errors during program execution
10+
11+The Free Pascal Compiler inserts code to detect a large number of error situations which might occur during program execution (eg divide by zero). If such an error situation occurs, the standard run-time library will terminate the program and print a runtime error number and the address at which the error occurred. See further [[runtime error|runtime errors]].
12+
13+If you encounter a runtime error while running your program and are unable to resolve it yourself, please use the FPC and Lazarus [Forums](https://forum.lazarus.freepascal.org/), write to the [Lazarus](https://lists.lazarus-ide.org/listinfo/lazarus) or [Free Pascal](https://www.freepascal.org/maillist.html) mailing list.
14+
15+## Bugs
16+
17+### If the bug is already known
18+
19+Use the FPC and Lazarus [Bug Tracker's](http://bugs.freepascal.org/set_project.php) search capabilities.
20+
21+Known issues. Tip: If you are experiencing problems, for example with TEdit.SelStart -\> try searching "SelStart" (in quotes). If the bug is known:
22+
23+- reopen if the issue is resolved or the issue is closed - use the **Reopen Issue** button.
24+- add your own note to the discussion if you received this error in another situation.
25+
26+To observe any changes to your bug report - use the **Monitor Issue** button.
27+
28+Note: You need to login to your account: [Login/Create an account](https://bugs.freepascal.org/login_page.php).
29+
30+### If the bug is not already known
31+
32+1. Go to the FPC and Lazarus [Bug Tracker](http://bugs.freepascal.org/set_project.php).
33+2. You must be logged in: [Login/Create account](https://bugs.freepascal.org/login_page.php).
34+3. Visit [Report Issue](http://bugs.freepascal.org/bug_report_advanced_page.php). Fill in as many fields as possible. The more accurate the better.
35+
36+- The **OS and Product Version** fields are especially important. If the data is not enough, they will not help you! Don't forget to mention the system features (big endian or 64-bit).
37+- It is often helpful to send in a small test program to resolve the problem as soon as possible.
38+- If you find graphic artifacts, it would not be superfluous to send a screenshot (in **png** or **jpeg**, but **not** in BMP!).
39+- If it fails, try creating a backtrace. More information - [[Creating a Backtrace with GDB]].
40+- If possible, observe the behaviour of the buggy program on different platforms or with different widgetsets.
41+
42+It is also possible to get a bug fixed by paying for a solution, see [[Bounties]].
43+
44+## See also
45+
46+- [[Lazarus Help]].
47+- [[Forum|How to use the Forums]].
48+- [[How do I create a bug report]].
49+- [[Creating A Patch]].
50+- [[Tips on writing bug reports]].
51+
52+---
53+*From the Free Pascal wiki, page "error messages", as it stood on 2023-04-19 after a change by Xhajt03, out of the wiki's dump of 2024-05-26. 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