Re: Excessive "fd" bytes at its tail of heap allocation
Jack wrote:
It is similar to the eariler case I posted in here,
as it suffered from memory leaks as well.
There's nothing wrong in the code you showed. The problem must be in the =
code you didn't show.
00 00 00 00 00 00 00....
fd fd fd fd
I've checked many places including the opened file itself and the =
stack..
This is normal. In a debug build, when you allocate memory, the actual =
allocation is slightly larger than what you asked for, and the block is =
filled with FD pattern. This serves two purposes: a) when you deallocate =
this block, the code in debug library checks that the extra allocated =
memory is still filled with FD pattern: if it's not, it knows you've =
overrun the buffer, and asserts; and b) while debugging, if you see, =
say, a field in a structure filled with FD pattern, it's a good =
indication that you forgot to initialize it.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not =
necessarily a good idea. It is hard to be sure where they are going to =
land, and it could be dangerous sitting under them as they fly overhead. =
-- RFC 1925