X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4AF30A85.5070208@users.sourceforge.net> Date: Thu, 05 Nov 2009 11:25:25 -0600 From: "Yaakov (Cygwin/X)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.4pre) Gecko/20090915 Thunderbird/3.0b4 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: malloc overrides References: <4AF29EC2.2050808@users.sourceforge.net> <4AF2D091.4030508@gmail.com> In-Reply-To: <4AF2D091.4030508@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 05/11/2009 07:18, Dave Korn wrote: >> extern void _exit (int); >> extern char* strdup (const char*); > > static int are_we_stuck = 1; >> >> char* malloc(unsigned n) { > are_we_stuck = 0; >> return 0; >> } >> >> int main(void) { >> strdup("yo"); > _exit (are_we_stuck); >> } > > FTFY. Funny, as I went to sleep last night I thought of just that solution. In practice, though, while it doesn't hang, it doesn't give the correct answer either. As Corinna said, the malloc override needs to be functional, in that it allocates memory which can then be free()d. So this isn't going to be quite so simple. :-( Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple