From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <79a157e0af8513bb08989abd589b0e27@terzarima.net>
From: Charles Forsyth <forsyth@terzarima.net>
Date: Thu,  3 Mar 2005 09:18:00 +0000
To: rs_rlab@mail.ru, 9fans@cse.psu.edu
Subject: Re: [9fans] realloc
In-Reply-To: <582542421.20050303081338@mail.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc:
Topicbox-Message-UUID: 1e4a06cc-ead0-11e9-9d60-3106f5b1d025

>>But why stk() in acid show last executed function (in my program) as realloc?

that's the first point at which the run-time system detected
that some hidden values it had planted at malloc/realloc had
been overwritten.  in general unless the allocated area lies
right at the limit of the process's data space you won't
get a trap because memmove is still accessing valid memory locations
even if the locations and the data are not what you really intended.
nothing untoward happened under windows because windows does
not (apparently) attempt to detect this common programming error,
or if it does, the scheme it uses was ineffective in your case.