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

do what I suggested in my earlier post.
2 copies of the datastructure A and B. you only need to malloc them once at the beginning and also since only one thread manipulates the data, right?

When you're in a situation where you need to 'slide' the data to the right, just memcpy from the current to the new and offset by the sizeof_int16_t). No janky hanky panky and can't possibly have CPU or OS side-effects.

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