search for: dw_form_ref

...is issue both on GDB and LLDB maillists. Unfortunately > it's hard or impossible to fix it on debugger side. > Errr, i posited a solution on the gdb mailing list that i haven't seen shot down so far, that doesn't require linkage names, it only requires one new attribute that is a DW_FORM_ref, and very cheap. I also wrote the RTTI code for GDB :) Currently what debugger has to do is to demangle RTTI name and try to match > it to DW_AT_name attribute to find type. As you can see it does not work > for any of 3 examples. > > I've asked about the problem on G++ maillist,...

Hi all, As you may know modern C++ debuggers (GDB and LLDB) support dynamic type identification for polymorphic objects, by utilizing C++ RTTI. Unfortunately this feature does not work with Clang and GDB >= 7.x . The last compiler that worked well was G++ 6.x I've asked about this issue both on GDB and LLDB maillists. Unfortunately it's hard or impossible to fix it on debugger side.

...DB maillists. Unfortunately >> it's hard or impossible to fix it on debugger side. >> > > Errr, i posited a solution on the gdb mailing list that i haven't seen > shot down so far, that doesn't require linkage names, it only requires one > new attribute that is a DW_FORM_ref, and very cheap. > FWIW, for C++ at least, neither Clang nor GCC (6.3) produce any DWARF to describe the vtable itself (they describe the vtable pointer inside the struct, but not the constant vtable array) - so it'll be a bit more than one attribute, but the bytes describe the vtable (as a...

...DB maillists. Unfortunately >> it's hard or impossible to fix it on debugger side. >> > > Errr, i posited a solution on the gdb mailing list that i haven't seen > shot down so far, that doesn't require linkage names, it only requires one > new attribute that is a DW_FORM_ref, and very cheap. > > I also wrote the RTTI code for GDB :) > > Currently what debugger has to do is to demangle RTTI name and try to >> match it to DW_AT_name attribute to find type. As you can see it does not >> work for any of 3 examples. >> >> I've asked a...

...t; Unfortunately it's hard or impossible to fix it on debugger side. >>> >> >> Errr, i posited a solution on the gdb mailing list that i haven't seen >> shot down so far, that doesn't require linkage names, it only requires one >> new attribute that is a DW_FORM_ref, and very cheap. >> > > FWIW, for C++ at least, neither Clang nor GCC (6.3) produce any DWARF to > describe the vtable itself (they describe the vtable pointer inside the > struct, but not the constant vtable array) - so it'll be a bit more than > one attribute, but the byt...

...#39;s hard or impossible to fix it on debugger side. >>>> >>> >>> Errr, i posited a solution on the gdb mailing list that i haven't seen >>> shot down so far, that doesn't require linkage names, it only requires one >>> new attribute that is a DW_FORM_ref, and very cheap. >>> >> >> FWIW, for C++ at least, neither Clang nor GCC (6.3) produce any DWARF to >> describe the vtable itself (they describe the vtable pointer inside the >> struct, but not the constant vtable array) - so it'll be a bit more than >> on...

...is issue both on GDB and LLDB maillists. Unfortunately it's hard or impossible to fix it on debugger side. > > Errr, i posited a solution on the gdb mailing list that i haven't seen shot down so far, that doesn't require linkage names, it only requires one new attribute that is a DW_FORM_ref, and very cheap. > > I also wrote the RTTI code for GDB :) > > Currently what debugger has to do is to demangle RTTI name and try to match it to DW_AT_name attribute to find type. As you can see it does not work for any of 3 examples. > > I've asked about the problem on G+...

...ible to fix it on debugger side. >>>>> >>>> >>>> Errr, i posited a solution on the gdb mailing list that i haven't seen >>>> shot down so far, that doesn't require linkage names, it only requires one >>>> new attribute that is a DW_FORM_ref, and very cheap. >>>> >>> >>> FWIW, for C++ at least, neither Clang nor GCC (6.3) produce any DWARF to >>> describe the vtable itself (they describe the vtable pointer inside the >>> struct, but not the constant vtable array) - so it'll be a bit m...

...bugger side. >>>>>> >>>>> >>>>> Errr, i posited a solution on the gdb mailing list that i haven't seen >>>>> shot down so far, that doesn't require linkage names, it only requires one >>>>> new attribute that is a DW_FORM_ref, and very cheap. >>>>> >>>> >>>> FWIW, for C++ at least, neither Clang nor GCC (6.3) produce any DWARF >>>> to describe the vtable itself (they describe the vtable pointer inside the >>>> struct, but not the constant vtable array) - so...

...;>>>>> >>>>>> >>>>>> Errr, i posited a solution on the gdb mailing list that i haven't >>>>>> seen shot down so far, that doesn't require linkage names, it only requires >>>>>> one new attribute that is a DW_FORM_ref, and very cheap. >>>>>> >>>>> >>>>> FWIW, for C++ at least, neither Clang nor GCC (6.3) produce any DWARF >>>>> to describe the vtable itself (they describe the vtable pointer inside the >>>>> struct, but not the constant...

...;> >>>>>>> >>>>>>> Errr, i posited a solution on the gdb mailing list that i haven't >>>>>>> seen shot down so far, that doesn't require linkage names, it only requires >>>>>>> one new attribute that is a DW_FORM_ref, and very cheap. >>>>>>> >>>>>> >>>>>> FWIW, for C++ at least, neither Clang nor GCC (6.3) produce any DWARF >>>>>> to describe the vtable itself (they describe the vtable pointer inside the >>>>>> struct,...

...;> >>>>>>> >>>>>>> Errr, i posited a solution on the gdb mailing list that i haven't >>>>>>> seen shot down so far, that doesn't require linkage names, it only requires >>>>>>> one new attribute that is a DW_FORM_ref, and very cheap. >>>>>>> >>>>>> >>>>>> FWIW, for C++ at least, neither Clang nor GCC (6.3) produce any DWARF >>>>>> to describe the vtable itself (they describe the vtable pointer inside the >>>>>> struct,...