https://bugs.kde.org/show_bug.cgi?id=517974
Mark Wielaard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Mark Wielaard <[email protected]> --- (In reply to Florian Krohm from comment #2) > (In reply to Paul Floyd from comment #1) > > > > As far as I know most of these failures are due to debuginfo. I don't know > > DWARF well enough to say whether this is because LLVM DWARF lacks elements > > that are present GCC or if the information is there but our DWARF reader is > > skipping over it. I suspect the latter. > > > > Yes, the following DW_OP_...s are not supported: > - DW_OP_form_tls_address 0x9b > - DW_OP_addrx 0xa1 > Whenever --read-var-info=yes is given those missing DW_OPs are being > warned about > and cause the test to fail. Unfortunately, I do not know how to add support > for those. > Is there a resident DWARF expert around? We do handle DW_OP_GNU_push_tls_address which might (or might not) be a pre-standardized variant of DW_OP_form_tls_address. DW_OP_addrx uses an index into an indirection table (.debug_addr) to get the actual address, so shouldn't be too hard to handle, but does need tracking an extra debug section. -- You are receiving this mail because: You are watching all bug changes.
