DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 61Q2asAk784252
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 260224BA2E0D
Date: Wed, 25 Feb 2026 18:36:29 -0800 (PST)
To: KENNON J CONRAD via Cygwin <cygwin@cygwin.com>,
        Matthias Andree <matthias.andree@gmx.de>
Message-ID: <1473298364.1505022.1772073389271@connect.xfinity.com>
In-Reply-To: <628046084.1504961.1772073184619@connect.xfinity.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>
 <858962676.1493082.1772049407251@connect.xfinity.com>
 <4f67089b-a064-49f0-bd00-c9acdf507903@gmx.de>
 <628046084.1504961.1772073184619@connect.xfinity.com>
Subject: Re: Memmove causing program crashes, giving SIGTRAP in GDB(?)
MIME-Version: 1.0
Importance: Normal
Precedence: list
From: KENNON J CONRAD via Cygwin <cygwin@cygwin.com>
Reply-To: KENNON J CONRAD <kennonconrad@comcast.net>
Content-Type: text/plain; charset="utf-8"
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

I mean memmove, not memset.

> On 02/25/2026 6:33 PM PST KENNON J CONRAD via Cygwin <cygwin@cygwin.com> wrote:
> 
>  
> Thanks.  I have cygwin-debuginfo 3.6.6-1 on both computers now and have put the failing memset back in the code.  It may take a day or so to get it to crash again.
> 
> > On 02/25/2026 2:31 PM PST Matthias Andree via Cygwin <cygwin@cygwin.com> wrote:
> > 
> >  
> > Am 25.02.26 um 20:56 schrieb KENNON J CONRAD via Cygwin:
> > > Hi Brian,
> > >
> > >     Thanks!  Should the cygwin-debuginfo package be installed on the computer that is compiling the code or the computer that is running the code.  I currently only have it installed on the computer that is running the code, not the one that is compiling the code.
> > 
> > Kennon,
> > 
> > Debug information (symbols and stuff) needs to be on the computer that 
> > is *debugging* the code. That often is the same computer that is 
> > *running* the code - (unless gdbserver or similar remote debugging forms 
> > come into play). Be sure that the version of the -debuginfo package 
> > matches the relevant binary you are debugging exactly.
> > 
> > Best regards
> > 
> > 
> > -- 
> > 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

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