[Lldb-commits] [PATCH] D12757: Fix prologue end handling when code compiled by gcc

Greg Clayton via lldb-commits lldb-commits at lists.llvm.org
Tue Sep 15 14:11:03 PDT 2015

clayborg added a comment.

Maybe we can try still removing duplicates, but remembering the first index where we had a duplicate line entry. If we don't get a prologue end, then we got back to the index we remembered for the first duplicate and if it is valid, modify that entry to say "prologue_end = true"?

One other questions for clarification: Is GCC emitting prologue_end, but only emitting it on the first line entry? And then we overrwrite it with the second and remove the prologue_end, or does GCC just plain not emit prologue_end? If so, what happens when we have a line table that doesn't have two entries for the prologue with the same address? Do we just not have a prologue_end in a sequence in that case?


More information about the lldb-commits mailing list