Can opdebugger be built with FPC 3.2.2 and used with Blaise ?

[Schmitty2005]

I was able to pasbuild compile from the root directory, and pasbuild showed 'success. I moved the pdr` executable into my system path, and I get the CLI message. This was built with FPC 3.2.2.

$ pdr
Usage: pdr [--verbose] [--version] <binary> [<argument> ...]

Debug an Object Pascal program using OPDF debug information.

Options:
  --version      - Show version information and exit
  --verbose, -v  - Enable diagnostic output at startup

Arguments:
  <binary>       - Path to the binary to debug
  <argument>     - Command-line arguments to pass to the program

Examples:
  pdr ./myprogram
  pdr --verbose ./myprogram
  pdr ./myprogram arg1 arg2 arg3

When I use blaise, it does not output the .opdf or .s files.
./blaise --source source.pas --debug-opdf --output source

Is this a blaise issue, or do I need to build with FPC 3.3.1 ?

[Schmitty2005]

Pasbuild Output with FPC 3.2.2 :

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS [  0.189 s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] opdf-lib ........ SUCCESS [  0.228 s]
[INFO] pdr-core ........ SUCCESS [  0.441 s]
[INFO] pdr-adapters .... SUCCESS [  0.403 s]
[INFO] pdr-cli ......... SUCCESS [  0.321 s]
[INFO] tools ........... SUCCESS [  0.189 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.582 s
[INFO] ------------------------------------------------------------------------

[graemeg]

Yes, the whole opdebugger repository can be built with FPC 3.2.2 and FPC 3.2.3 (FreeBSD - just tested 20 minutes ago :-D). The only time you need a special build of FPC 3.3.1 is if you want FPC to create binaries that use OPDF debugging information.

But as I'm mostly using Blaise compiler, which has 1st class built-in OPDF debugging support, the FPC 3.3.1 is not a requirement when using Blaise.

The .opdf and .opdf.s files were really limitations of the way FPC was written. If I recall [it's been a while], I did manage to get FPC to produce binaries with embedded OPDF data inside the binary. No external files. I'll have to double-check.

Blaise always generates OPDF data embedded in the generated binaries. I guess I must have some stale README or documentation somewhere, that needs updating. I'll make sure to do that.

[Schmitty2005]

Thank you for the clarification!

In the readme :

3. Building
   Requires PasBuild and FPC 3.3.1+ with OPDF support (-gO flag):

It was not clear that FPC 3.2.2 can be used to build. And with lots of new features in 3.3.1, I thought it may have been a requirement.

[graemeg]

Think of this 'opdebugger' repo as what's defining the specification of OPDF format (which it is).

The cli pdr is the consumer of the opdf information. 'pdr' can consume the debug information, no matter what or who created that debug information. All the code is built with FPC 3.2.2 (simply because it predates Blaise), but it's the opdf specification that's important.

The only producers of OPDF debug info so far are Blaise and my branch in FPC 3.3.1. As long as they adhere to the opdf specification, pdr should be able to consume it.

[graemeg]

I'll also try and improve the README to make it easier to understand. Thanks for the feedback.