aurore-poirier wrote: Thanks for your comments! I figured this out in a quite big setup involving OpenOCD, I'll try to generate a minimal ELF to reproduce the behavior and will come back to you. Your second point can be addressed quite easily: i am working with a binary where some symbols are generated from linker scripts, hence they might be valid addresses, but they don't have proper ELF tags (it's not even possible to specify ELF tags in linker scripts as they are too generic). They end up identified as `eSymbolInvalid` when loaded in LLDB. In the case of OpenOCD, it can try to fetch them. Some might even be hard-coded data, not going through an address in the binary (explaining the presence of the [check and raw value return](https://github.com/llvm/llvm-project/pull/200134/changes/BASE..a8dcabf9cad6b64cf35cb06f902e0ecc6108c76a#diff-82cb38d9af6d5239660a958e92a0dbe5d953a5f371b4b7dc8b2002a6264ab558R4207-R4209)). Testing it showed that GDB returns them despite them not being proper addresses, i will also try to showcase it in the minimal example.
https://github.com/llvm/llvm-project/pull/200134 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
