It is time to get some feedback on how FpDebug behaves in the wild.

If you want to test it, you need:
- Lazarus 2.1  revision 62049 (dated 13 Oct 2019) or higher/later
- Fpc any version that above Lazarus works with.
  If you use FPC trunk, you should aim for revision 43183 or higher.
     earlier trunk will cause bad results inspecting bitpacked arrays
     3.0.4 is fine
     3.2 may depend on what gets merged when, and FpDebug may need amendments if certain fpc fixes are merged.

As for what to expect:  https://wiki.lazarus.freepascal.org/FpDebug

When reporting back:
- Your Lazarus and FPC version/revision.
- Your OS (with version and 32 or 64 bit)
- Your IDE is 32 or 64 bit
- Your FPC is 32 or 64 bit
- Your target app is 32 or 64 bit (and indicate if it was cross compiled, by an FPC with different bitness) - In case something failed, log output of (or preferably, a reproducible testcase)   lazarus.exe   --debug-log=file --log-enable=DBG_STATE,DBG_DATA_MONITORS,DBG_ERRORS,DBG_VERBOSE,DBG_WARNINGS,DBG_BREAKPOINTS,DBG_FPDEBUG_VERBOSE,FPDBG_BREAKPOINT_ERRORS,FPDBG_BREAKPOINTS

Thank you



--
_______________________________________________
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus

Reply via email to