Difference between revisions of "Debugging Compiler"

From Free Pascal wiki
Jump to navigationJump to search
(Created page with "Here are some hints on debugging FPC compiler itself ==Debugging FPC Hints== * useful procedure to place a breakpoint in is GenerateError. It's called for any kind of compilat...")
 
m
Line 4: Line 4:
 
* like gcc there are some verbosity options to show internal representations like -vp -vv,
 
* like gcc there are some verbosity options to show internal representations like -vp -vv,
 
* Place a breakpoint in lazarus. A .lpi is in the compiler/ director (using Lazarus IDE)
 
* Place a breakpoint in lazarus. A .lpi is in the compiler/ director (using Lazarus IDE)
 +
[[Category:FPC]]
 +
[[Category:FPC Development]]

Revision as of 20:48, 11 April 2021

Here are some hints on debugging FPC compiler itself

Debugging FPC Hints

  • useful procedure to place a breakpoint in is GenerateError. 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. A .lpi is in the compiler/ director (using Lazarus IDE)