> It's assigned a memory location of 0x6e615c31
Which looks a lot like a string fragment of "na\1"
The \ is telling, does it look like part of a filename perhaps?
I'm betting that you're copying a string into some other allocated memory, and this is where you observe the trashing of memory as a crash.
Salem
Posting Sage
11,531 posts since Dec 2005
Reputation Points: 5,862
Solved Threads: 953
> debugger is that the 1st data item is allocated at: 0x0426c814, the 2nd at: 0x6674725c & so on...
Let me re-iterate my previous post.
Your 2nd address again looks like a printable string ("ftr\"), so you're mistaking bugs elsewhere in your code as something else.
If there is only one malloc, then all the data is contiguous.
Salem
Posting Sage
11,531 posts since Dec 2005
Reputation Points: 5,862
Solved Threads: 953