[new release] owee (0.8)

[let-def]

OCaml library to work with DWARF format

• Project page: https://github.com/let-def/owee

CHANGES:

Sun Feb 16 08:22:39 AM JST 2025

• Add program header parsing by @JosiahWhite
  (Needed to improve Magic-Trace support for Rust programs,
  or, more generallry, ELF spec)

[shonfeder]

Thanks for the update!

Tests are failing:

distributions

alpine-3.21-ocaml-4.14
owee.0.8
tests (failed: The compilation of owee.0.8 failed at "dune build -p owee -j 39 @install @runtest".)
alpine-3.21-ocaml-5.3
owee.0.8
tests (failed: The compilation of owee.0.8 failed at "dune build -p owee -j 255 @install @runtest".)
opensuse-15.6-ocaml-4.14
owee.0.8
tests (failed: The compilation of owee.0.8 failed at "dune build -p owee -j 255 @install @runtest".)
opensuse-15.6-ocaml-5.3
owee.0.8
tests (failed: The compilation of owee.0.8 failed at "dune build -p owee -j 255 @install @runtest".)
opensuse-tumbleweed-ocaml-4.14
owee.0.8
tests (failed: The compilation of owee.0.8 failed at "dune build -p owee -j 255 @install @runtest".)
opensuse-tumbleweed-ocaml-5.3
owee.0.8
tests (failed: The compilation of owee.0.8 failed at "dune build -p owee -j 71 @install @runtest".)

Let us know if you need a hand troubleshooting.

[JosiahWhite]

@let-def This looks to be due to the compiled test-4.bin/test-5.bin files containing extra debug symbols for c runtime functions

[let-def]

@let-def This looks to be due to the compiled test-4.bin/test-5.bin files containing extra debug symbols for c runtime functions

Yes, thanks for looking into it. The simplest fix is to test only for debug lines from the file being tested by grepping the output.

An alternative approach would be to test only object files, not linked binaries. However, GCC (at least mine) generates compressed debug line sections for object files, which would require updating the debug_line support to handle zlib and possibly zstd sections. This is another can of worms that might be addressed in a future version.

Separately testing binaries is still worthwhile, so I will use the "grep" workaround for now, unless anyone knows of a more principled approach.

[let-def]

@shonfeder: The build error on s390x can be ignored I think. The support is limited to x86-64 for the time being.

[shonfeder]

@let-def than you for the CI review and for the fixes!

The last thing I am seeing is this failure on Windows:

  #=== ERROR while compiling owee.0.8 ===========================================#
  # context     2.3.0 | win32/x86_64 | ocaml.5.3.0 | file://D:/a/opam-repository/opam-repository
  # path        D:\opamroot\default\.opam-switch\build\owee.0.8
  # command     D:\opamroot\default\bin\dune.exe build -p owee -j 3 @install
  # exit-code   1
  # env-file    D:\opamroot\log\owee-1816-626a32.env
  # output-file D:\opamroot\log\owee-1816-626a32.out
  ### output ###
  # File "src/dune", line 5, characters 36-46:
  # 5 |  (foreign_stubs (language c) (names owee_stubs))
  #                                         ^^^^^^^^^^
  # (cd _build/default/src && D:\opamroot\default\bin\x86_64-w64-mingw32-gcc.exe -O2 -fno-strict-aliasing -fwrapv -mms-bitfields -fdiagnostics-color=always -g -I D:/opamroot/default/lib/ocaml -I D:/opamroot/default/lib/ocaml\unix -o owee_stubs.o -c owee_stubs.c)
  # owee_stubs.c:18:10: fatal error: dlfcn.h: No such file or directory
  #    18 | #include <dlfcn.h>
  #       |          ^~~~~~~~~
  # compilation terminated.

Should we perhaps mark this as unavailable on windows?