From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Date: Fri, 11 Apr 2025 19:37:18 +0000 (+0200)
Subject: Fix typo:  segement -> segment
X-Git-Tag: VALGRIND_3_25_0~48
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=50d1a471cd86ba82f3bc4e79943b43bf9193d8cb;p=thirdparty%2Fvalgrind.git

Fix typo:  segement -> segment

No impact, typo in a comment.
---

diff --git a/coregrind/m_ume/elf.c b/coregrind/m_ume/elf.c
index 67d3139d2..5f2ac1fed 100644
--- a/coregrind/m_ume/elf.c
+++ b/coregrind/m_ume/elf.c
@@ -514,7 +514,7 @@ Bool VG_(match_ELF)(const void *hdr, SizeT len)
      the furthest-along mapping it creates.  The executable is mapped
      starting at EBASE, which is usually read from it (eg, 0x8048000
      etc) except if it's a PIE, in which case aspacem is queried for
-     the first adequately sized segement.
+     the first adequately sized segment.
 
      The returned address is recorded in info->brkbase as the start
      point of the brk (data) segment, as it is traditional to place