DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 61R257Ap1390120
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 61R257Ap1390120
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=jUPHBpTD
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org EC60B4BA23C3
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1772157907;
	bh=zFI6e1LKL7rm94KeI3W3IgNVWO1Qrr23syTZ6v8/vS0=;
	h=Date:To:Cc:In-Reply-To:References:Subject:List-Id:
	List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	From:Reply-To:From;
	b=jUPHBpTD47UPJGVdV2kUWdDLc6GVrfO9oPjHkkjJSTUrEwsGfaFnKmYCeBN32MiXB
	ssOGDEr6j/O4+r6/8jt7LG4wtKQcNgJtuDgJdrTl1ofyQwgnpXge+tWSILUj6ObZwQ
	hK+TwJsBPtLEG8PwWxpLhhVkbdvlsTdQCCkc2cEU=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 3E5EB4BA2E15
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org 3E5EB4BA2E15
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1772157887; cv=none;
	b=Ks/ey/vGHr5Nq+/aI2WphJjDkgT1aACqIpWyFjPTEqhrp0K82PMuZ/2inIvMaOBoIGhFSi9ywPyN1rcTbPGhCIKcEuocclq55/BYkMjTMRnlfntAvOA2OJnzLBVyTj6gEr6oAytCWAb+Zwt8LlMuEaOsxNL3qaKg6mmIr7QAxBU=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1772157887; c=relaxed/simple;
	bh=unKo9WtA0ah1uCcvfZQTeSM2q+FHluJXpyiek5kTiiA=;
	h=DKIM-Signature:Date:From:To:Message-ID:Subject:MIME-Version;
	b=sR3wSgEAs+8U/aJlNsqknQPHXIeQwzFs3VTcrD/+iLeuUWOF/xVHovwKm2ZSSECLxH+Uaohof9WuztiXQeN8PvcR7vLYpfbYJD9g2+oiGZ2Uml8cmA7ig+G1KBYCI95YiWOq26qrKlVrpPUX3MV2QhEnnHYBlMIKstlUaSDIg+s=
ARC-Authentication-Results:	i=1; server2.sourceware.org
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 3E5EB4BA2E15
Date:	Thu, 26 Feb 2026 18:04:43 -0800 (PST)
To:	Eliot Moss <moss AT cs DOT umass DOT edu>,
	Dimitry Andric <dimitry AT unified-streaming DOT com>
Cc:	KENNON J CONRAD via Cygwin <cygwin AT cygwin DOT com>
Message-ID:	<1093316506.1533154.1772157883568@connect.xfinity.com>
In-Reply-To:	<399745a1-429a-ebb4-0f67-c32f6282caa6@cs.umass.edu>
References:	<547312365 DOT 1464244 DOT 1771958282029 AT connect DOT xfinity DOT com>
	<aZ7PrbisVR1R4A7v AT dimstar DOT local DOT net>
	<1670201592 DOT 1489273 DOT 1772043520008 AT connect DOT xfinity DOT com>
	<e91d8b5b-2690-4271-aa74-e6226440e33d AT SystematicSW DOT ab DOT ca>
	<1044918836 DOT 1507810 DOT 1772086967212 AT connect DOT xfinity DOT com>
	<1579472684 DOT 1508349 DOT 1772092747339 AT connect DOT xfinity DOT com>
	<aaABFf5iEowV1l7I AT xps13>
	<1148572549 DOT 1808180 DOT 1772097444036 AT mail DOT yahoo DOT com>
	<1901597260 DOT 1508573 DOT 1772100378936 AT connect DOT xfinity DOT com>
	<0C965DD0-856E-41FF-B5A4-15E472292A32 AT unified-streaming DOT com>
	<483908609 DOT 1508714 DOT 1772103775739 AT connect DOT xfinity DOT com>
	<2346fd41-2500-0db6-5849-6788174b5a1d AT cs DOT umass DOT edu>
	<1462848037 DOT 1521935 DOT 1772136952077 AT connect DOT xfinity DOT com>
	<399745a1-429a-ebb4-0f67-c32f6282caa6 AT cs DOT umass DOT edu>
Subject:	Re: Memmove causing program crashes, giving SIGTRAP in GDB(?)
MIME-Version:	1.0
X-Priority:	3
Importance:	Normal
X-Mailer:	Open-Xchange Mailer v7.10.6-Rev83
X-Originating-IP:	::ffff:50.47.202.14
X-Originating-Port:	16074
X-Originating-Client:	open-xchange-appsuite
X-CMAE-Envelope:	MS4xfISSiyXReAKADmNrtFStOY7dwcE/VJabCQjMFZXGmSX4I+ziXuAUb676qcIth6pSZMRZEluU8EGF1WVKPrtNx1nmxxXJJpuNXd2uRHVy/F+67wpxgthI
	ri4PVbS6/n42orQbnMEsjHMaTSPM7+zwMaWd55hJDW4tiPwUlGfs2gzlUpXfai/qCjNX5IN7RrRb6agvbIDDqDoXQalSuFdm16EoY0vO/KdSL98vvnb7GeJO
	evk3f4pfo3A9aKHObLqr+Q7Q6kz2qCtYiMd+uZXSeg+teoYiDulkSqyoqojsVyX9
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	KENNON J CONRAD via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	KENNON J CONRAD <kennonconrad AT comcast DOT net>
Errors-To:	cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 61R257Ap1390120

Perhaps something like this?  Maybe I need to try a BIOS update?

Intel Haswell (and related architectures) processors may experience stability issues, including machine check errors (MCEs), due to a microcode bug related to REP MOVS (specifically REP MOVSB or REP MOVSQ) handling. These issues often cause system crashes or lockups, leading to microcode, BIOS/UEFI updates to resolve them. 
Debian Wiki
 +4
Issue: A high-rate of interrupts or specific memory operations can cause REP MOVS instructions to trigger Machine Check Errors (MCE) or internal errors (IERR) on older processors.
Affected Processors: The bug primarily impacts older Intel processors, including Haswell and Broadwell architectures.
Fix/Mitigation: The primary solution is to apply the latest motherboard BIOS/UEFI update, which contains the corrected microcode update (often labelled 20180108 or later).
Background: This is linked to Intel’s efforts to fix security vulnerabilities (like Spectre), where early patches for Haswell/Broadwell caused unexpected instability, requiring further refinements. 
Debian Wiki
 +4

-Kennon

> On 02/26/2026 2:30 PM PST Eliot Moss <moss AT cs DOT umass DOT edu> wrote:
> 
>  
> I know it's a low probability for a cause, but I wonder if either the
> hardware or the OS have some issue with proper restartability of the
> REP MOVSQ under some weird circumstance.  If the hardware/firmware
> does not save the in-flight register information correct (again, in
> some weird and rare situation) then restarting the instruction could
> fail.  Might be worth:
> 
> (a) trolling the web to see if there are reports of issues around this
>      instruction, Intel firmware fixes, etc.  (An instruction like REP
>      MOVSQ is almost certainly implemented with a microcode loop, etc.)
> 
> (b) trying this exact code with a substantially different CPU model
>      (which might tend to avoid any microcode bug in the model you're
>      using).
> 
> Again, low probability, but ...
> 
> Regards - EM

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -