Memmove causing program crashes, giving SIGTRAP in GDB(?)

[KENNON J CONRAD]

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