When you wrote: "Here is the code", followed by some code which was **NOT** the code (as revealed in post #7), you caused Stephan, (who was also working from a mobile device), to waste his time pointing out a problem which, apparently<sup>a</sup>, you were not having. Summaries and false characterization of a problem are highly likely to impede problem resolution. ---- a. The segmentation fault could easily have been produced by the very indexed access error exhibited in "the code" later disavowed, so the misrepresentation goes beyond mere distraction; it is positively misleading.