Hi,


this is a minor update to the previous version here:
https://sourceware.org/pipermail/gdb-patches/2020-November/173614.html

The only real change is here:

--- a/gdb/buildsym.c
+++ b/gdb/buildsym.c
@@ -429,7 +429,10 @@ struct block *
     {
       m_inline_end_vector.push_back (end_inclusive + 1);
       if (end_inclusive + 1 == start)
-       end_inclusive = start;
+       {
+         end_inclusive = start;
+         m_pending_addrmap_interesting = true;
+       }
     }
 
   if (m_pending_addrmap == nullptr)


The test case with an empty inline that triggered this
is from PR 25987.

It is a real-world code that triggers both an empty inline
function and the wrong call-stack immediately after
the inline.  So I added this test case as well.

So this fixes PR 25987 as well as a lot of issues with
debugging inlined functions in general.


Thanks
Bernd.