diff options
author | Alok Kumar Sharma <AlokKumar.Sharma@amd.com> | 2022-05-22 21:46:06 +0530 |
---|---|---|
committer | Kavitha Natarajan <kavitha.natarajan@amd.com> | 2022-05-22 21:46:06 +0530 |
commit | 6f9b09edaee43ea34d34b1998fe7b844834f251a (patch) | |
tree | c0ae8cd64603201c664070d06c2efdc9dcee4bab /gdb/ChangeLog-1991 | |
parent | cb3a7614feb82ffdc25161bf60529116c6112ab3 (diff) | |
download | gdb-6f9b09edaee43ea34d34b1998fe7b844834f251a.zip gdb-6f9b09edaee43ea34d34b1998fe7b844834f251a.tar.gz gdb-6f9b09edaee43ea34d34b1998fe7b844834f251a.tar.bz2 |
Accept functions with DW_AT_linkage_name present
Currently GDB is not able to debug (Binary generated with Clang) variables
present in shared/private clause of OpenMP Task construct. Please note that
LLVM debugger LLDB is able to debug.
In case of OpenMP, compilers generate artificial functions which are not
present in actual program. This is done to apply parallelism to block of
code.
For non-artifical functions, DW_AT_name attribute should contains the name
exactly as present in actual program.
(Ref# http://wiki.dwarfstd.org/index.php?title=Best_Practices)
Since artificial functions are not present in actual program they not having
DW_AT_name and having DW_AT_linkage_name instead should be fine.
Currently GDB is invalidating any function not havnig DW_AT_name which is why
it is not able to debug OpenMP (Clang).
It should be fair to fallback to check DW_AT_linkage_name in case DW_AT_name
is absent.
Diffstat (limited to 'gdb/ChangeLog-1991')
0 files changed, 0 insertions, 0 deletions