Difference between revisions of "Debugging Compiler"
From Free Pascal wiki
Jump to navigationJump to searchm |
m (→Debugging FPC Hints: Fix typos; add debugging category) |
||
| Line 1: | Line 1: | ||
Here are some hints on debugging FPC compiler itself | Here are some hints on debugging FPC compiler itself | ||
==Debugging FPC Hints== | ==Debugging FPC Hints== | ||
| − | * useful procedure to place a breakpoint | + | |
| − | * | + | * A useful procedure in which to place a breakpoint is [code]GenerateError[/code]. It's called for any kind of compilation error (syntax error, type error, assembler reader error, internal error, ...). |
| − | * Place a breakpoint in | + | |
| + | * Like gcc there are some verbosity options to show internal representations like -vp -vv | ||
| + | |||
| + | * Place a breakpoint in Lazarus. An .lpi is in the compiler/directory (using Lazarus IDE). | ||
| + | |||
[[Category:FPC]] | [[Category:FPC]] | ||
| + | [[Category:Debugging]] | ||
[[Category:FPC development]] | [[Category:FPC development]] | ||
[[Category:FPC internals]] | [[Category:FPC internals]] | ||
Revision as of 03:15, 12 April 2021
Here are some hints on debugging FPC compiler itself
Debugging FPC Hints
- A useful procedure in which to place a breakpoint is [code]GenerateError[/code]. It's called for any kind of compilation error (syntax error, type error, assembler reader error, internal error, ...).
- Like gcc there are some verbosity options to show internal representations like -vp -vv
- Place a breakpoint in Lazarus. An .lpi is in the compiler/directory (using Lazarus IDE).
