Florian Märkl

Sure, but that too will take a long time until the update is widespread enough for us to use.

> > * This is rather cumbersome because of meson's extremely limited support for path operations. > > [mesonbuild/meson#7908](https://github.com/mesonbuild/meson/pull/7908) This should indeed solve it cleanly.

In progress: https://github.com/rizinorg/rizin/tree/serialize-io

This is essentially a special cases of scope for variables. We can assign a set of addresses (represented by one or multiple intervals) to each variable that defines its scope....

After #880, the line info is available in a format-agnistic way in `RzBinObject.lines` so from the perspective of querying the info after it has been loaded, this is already done....

3 kinds of warnings were enhanced/removed in 32d937963880b32c9f1e01a8213445631800fc1f and 4f42e6f3b5792ab5f82739f17a777d55b9ae7563. Please give concrete examples of other warnings that do not give good info.

First and second case (`harp-utils.c-gcc-arm64-O0.o`, `s_ceill.c-gcc-x86-O2.o`): Both of these also happen in Java Ghidra, please report to them primarily. Third and fourth case (`sv_bot.c-gcc-x64-O1.o`, `filetime.c-clang-x64-O0.o`): Only happen in rz-ghidra, but...

First two are fixed by https://github.com/NationalSecurityAgency/ghidra/commit/636102a409d0e34507de69d216a1b5736776ea6a, second two still present.

Either that or take the info from r2 directly if it has it somewhere.

This is already implemented, however in this case it seems it messes up the addresses for some reason. Can you share the binary?