Check for stack truncations in the link map code, surprisingly.

Author: Jlalond

lldb/source/Target/Process.cpp

@@ -6577,7 +6577,8 @@ static void AddSegmentRegisterSections(Process &process, ThreadSP &thread_sp,
   AddRegion(thread_local_region, true, ranges);
 }
 
-static void AddLinkMapSections(Process &process, CoreFileMemoryRanges &ranges) {
+static void AddLinkMapSections(Process &process, CoreFileMemoryRanges &ranges,
+                               std::set<addr_t> &stack_ends) {
   ModuleList &module_list = process.GetTarget().GetImages();
   Target *target = &process.GetTarget();
   for (size_t idx = 0; idx < module_list.GetSize(); idx++) {
@@ -6598,6 +6599,11 @@ static void AddLinkMapSections(Process &process, CoreFileMemoryRanges &ranges) {
     if (err.Fail())
       continue;
 
+    // Sometimes, the link map section is included in one of the stack memory
+    // ranges. In that case, we already saved a truncated version of that range
+    if (stack_ends.count(link_map_section.GetRange().GetRangeEnd()) == 0)
+      continue;
+
     AddRegion(link_map_section, true, ranges);
   }
 }
@@ -6754,7 +6760,7 @@ Status Process::CalculateCoreFileSaveRanges(const SaveCoreOptions &options,
     SaveOffRegionsWithStackPointers(*this, options, regions, ranges,
                                     stack_ends);
     // We need the link map for TLS data.
-    AddLinkMapSections(*this, ranges);
+    AddLinkMapSections(*this, ranges, stack_ends);
   }
 
   switch (core_style) {