On 4/17/2013 3:58 PM, alexander.elg...@external.t-systems.com wrote:
I got it, it was my fault, using dmalloc shows:
27 (ERROR_OVER_FENCE) failed OVER picket-fence magic-number check
It was a malloc(sizen) and and a strncpy(... sizen) ... ;(
Surprisingly this results in an error many mallocs later.
This is common for heap corruption errors, because production heap
implementations (not debug heaps) usually store the information about
each used/free area of memory close to that area for speed, and thus
overwriting that information has no effect until the heap happens to
be looking at that location during an unrelated heap operation much
later. If it doesn't crash then, the damage gets even worse as the
heap gets confused and does wrong things.
As a rule of thumb, whenever you see a crash in malloc/free/realloc
etc., it is usually due to earlier corruption, not the current stack.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com
Transformervej 29, 2730 Herlev, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
