Recent

Author Topic: How can I step into fppdf.pp when debug  (Read 1455 times)

loadymf

  • New member
  • *
  • Posts: 9
How can I step into fppdf.pp when debug
« on: December 18, 2023, 12:39:05 am »
 How can I step into fppdf.pp when debug,
I has use fppdf.pp to create pdf,but I went to debug the fppdf.pp code,cannot step into fppdf.pp

dsiders

  • Hero Member
  • *****
  • Posts: 1080
Re: How can I step into fppdf.pp when debug
« Reply #1 on: December 18, 2023, 12:55:05 am »
How can I step into fppdf.pp when debug,
I has use fppdf.pp to create pdf,but I went to debug the fppdf.pp code,cannot step into fppdf.pp

RTL and FCL are not built with debug information by default. See these links for more information:

https://forum.lazarus.freepascal.org/index.php?topic=39255.0
https://www.freepascal.org/docs-html/user/usersu73.html
Preview Lazarus 3.99 documentation at: https://dsiders.gitlab.io/lazdocsnext

cdbc

  • Hero Member
  • *****
  • Posts: 1083
    • http://www.cdbc.dk
Re: How can I step into fppdf.pp when debug
« Reply #2 on: December 18, 2023, 01:21:26 pm »
Hi
Quote
How can I step into fppdf.pp when debug,
I has use fppdf.pp to create pdf,but I went to debug the fppdf.pp code,cannot step into fppdf.pp
1) make directory in a tmp location of your choice eg: /home/user/tmp/__fppdf
2) copy the file "fppdf.pp" to your tmp-location
3) rename "fppdf.pp" in your tmp-location to "__fppdf.pp", remember the unit name inside the file  ;)
4) in your app change the uses to use "__fppdf" and include your tmp-location in "Project-Options-Path"
5) recompile your project with debug-info on.
6) now you should be able to step into the fppdf.pp source...
7) when you're done, simply change your uses clause back to "fppdf" and remove tmp-location from project options.
Give that a whirl and see what happens  8-)
HTH
Regards Benny
If it ain't broke, don't fix it ;)
PCLinuxOS(rolling release) 64bit -> KDE5 -> FPC 3.2.2 -> Lazarus 2.2.6 up until Jan 2024 from then on it's: KDE5/QT5 -> FPC 3.3.1 -> Lazarus 3.0

 

TinyPortal © 2005-2018