DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 61QApoPp1038463
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 3ADF54BA23E8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81.1.4\))
Subject: Re: Memmove causing program crashes, giving SIGTRAP in GDB(?)
In-Reply-To: <1901597260.1508573.1772100378936@connect.xfinity.com>
Date: Thu, 26 Feb 2026 11:50:26 +0100
Message-Id: <0C965DD0-856E-41FF-B5A4-15E472292A32@unified-streaming.com>
References: <547312365.1464244.1771958282029@connect.xfinity.com>
 <aZ7PrbisVR1R4A7v@dimstar.local.net>
 <1670201592.1489273.1772043520008@connect.xfinity.com>
 <e91d8b5b-2690-4271-aa74-e6226440e33d@SystematicSW.ab.ca>
 <1044918836.1507810.1772086967212@connect.xfinity.com>
 <1579472684.1508349.1772092747339@connect.xfinity.com>
 <aaABFf5iEowV1l7I@xps13> <1148572549.1808180.1772097444036@mail.yahoo.com>
 <1901597260.1508573.1772100378936@connect.xfinity.com>
To: KENNON J CONRAD <kennonconrad@comcast.net>
Precedence: list
From: Dimitry Andric via Cygwin <cygwin@cygwin.com>
Reply-To: Dimitry Andric <dimitry@unified-streaming.com>
Cc: KENNON J CONRAD via Cygwin <cygwin@cygwin.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>

Most memcpy/memmove implementations consist of an initial part that copies/moves any number of leading unaligned bytes, if necessary, followed by a main loop that copies/movies the bulk as words (32 or 64 bit depending on the architecture), and finally a part that copies/moves any number of tailing unaligned bytes.

The implementation you showed in assembly does just that. The main loop will use instructions that are supposed to only be used on aligned memory, but since the leader and trailer are handled separately, you should never run into an alignment exception at that point. My guess is that there is some sort of buffer overrun instead. If the overrun stays within a memory page, you won't notice it, but unrelated data will have been clobbered. However, if the overrun goes over a page boundary, you will get a page fault.

-Dimitry

> On 26 Feb 2026, at 11:06, KENNON J CONRAD via Cygwin <cygwin@cygwin.com> wrote:
> 
> Yes, movsq requires addess alignment.  Memmove however is not supposed to require alignment as it should work for chars, ints, etc.  It should handle alignment requirements before calling movsq.  That is something I want to verify.
> 
>> On 02/26/2026 1:17 AM PST matthew patton <pattonme@yahoo.com> wrote:
>> 
>> 
>> On Wed, Feb 25, 2026 at 11:59:07PM -0800, KENNON J CONRAD via Cygwin wrote:
>>> Okay, so now I learned about setting the frame and disassemble and see the memmove code:
>>> 
>>> Dump of assembler code for function memmove:
>> [snip]
>>> => 0x00007ff96ba812a9 <+137>:    rep movsq %ds:(%rsi),%es:(%rdi)
>> [snip]
>>> End of assembler dump.
>> 
>> movsq requires address alignment of 8 bytes.
>> What are the pointer addresses of the arguments to memmove()?
>> A SIGTRAP may result if the addresses are not 8-byte aligned.
>> 
>> 
>> 767 * 2 / 8 and 2633 * 2 / 8 would seem to violate that rule.
> 
> -- 
> 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


-- 
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