Dominic Fandrey

I'll look into it.

Can you fetch the repository and test the fix? Just run `make` and `obj/powerd++ -vfH 75:85`.

What kind of CPU do you have. Some CPUs require on offset applied to the measured value, which FreeBSD usually doesn't. So the displayed value is not necessarily the true...

The `` header should be located under `/usr/include/c++/v1/charconv`. Can you verify that? I would of course like a backtrace of the crash if you're willing to make a debug build...

Can you go to the ports directory and run the following commands: - `make -VMAKE_ENV -VMAKE_ARGS` - `printenv` - `which c++`

Can you try to build the port with `make -DWITH_DEBUG` and produce a backtrace of the crash?

I found a bug with the address sanitiser, I have a vague hope that that might have been the issue: https://github.com/lonkamikaze/powerdxx/commit/28e61dbd3c5ecbb43d161729b5afb18d38f40d76 Are you willing to test this?

No, it's not doing anything like that. To use the core dumps provided I also need the binary that was run, otherwise I cannot create a backtrace.

This is a stripped binary, no debugging symbols, can you test a binary built with `make debug paranoid`? On my system the resulting binary is 5 MB large.

It's very frustrating. I cannot get a backtrace out of the coredump, there's just a single frame, not being resolved to any function and if I run the binary myself,...