fix(debuginfo): resolve addresses in additional R-E LOAD segments

VG_(find_DebugInfo) used only di->text_avma/text_size for address→DI
lookup, which covers the section named ".text" — not the other
executable sections (.text.warm, .text.cold, .bolt.org.text) that
BOLT-optimized binaries place in a separate R-E PT_LOAD segment.
Addresses in that second segment fell through to ob=??? even though
the address-space manager already knew they were backed by the same
file.

Fall back to VG_(am_find_nsegment) and match the segment's filename
against debugInfo_list. Reproduced on cpython-3.14 standalone (uv's
distribution): obj-skip now catches py_trampoline_evaluator,
_PyFunction_Vectorcall.cold, and other functions that previously
escaped via ob=???.

Author: not-matthias

coregrind/m_debuginfo/debuginfo.c

@@ -2617,6 +2617,27 @@ DebugInfo* VG_(find_DebugInfo) ( DiEpoch ep, Addr a )
          return di;
       }
    }
+   /* Fallback for ELFs with multiple executable LOAD segments (e.g. BOLT-
+      optimized binaries: .bolt.org.text + .text + .text.warm + .text.cold
+      live in two separate R-E PT_LOAD segments). The text-range check above
+      only covers the section named ".text", so addresses in the other
+      executable region are missed and end up attributed to "???". Ask the
+      address-space manager which file backs this address, and match it to
+      a DebugInfo by filename. */
+   if (eq_DiEpoch(ep, VG_(current_DiEpoch)())) {
+      const NSegment* seg = VG_(am_find_nsegment)(a);
+      const HChar* filename;
+      if (seg != NULL && (filename = VG_(am_get_filename)(seg)) != NULL) {
+         for (di = debugInfo_list; di != NULL; di = di->next) {
+            if (!is_DI_valid_for_epoch(di, ep))
+               continue;
+            if (di->fsm.filename != NULL
+                && 0 == VG_(strcmp)(di->fsm.filename, filename)) {
+               return di;
+            }
+         }
+      }
+   }
    return NULL;
 }