Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 To: cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Joe Buehler Newsgroups: gmane.os.cygwin Subject: sporadic core dumps caused by atexit processing Date: Tue, 09 Jul 2002 09:45:16 -0400 Lines: 12 Message-ID: <3D2AE8EC.8000708@hekimian.com> NNTP-Posting-Host: hekimian.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1026222272 15691 206.205.138.10 (9 Jul 2002 13:44:32 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 9 Jul 2002 13:44:32 +0000 (UTC) User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en I am seeing sporadic core dumps whose cause appears to be a call to atexit(0). Maybe not, but the atexit data structure has a null function pointer in it when examined with gdb. This causes obvious problems when the process exits. The null pointer appears to always be at _fns[1], if that means anything to anyone. For the moment, I am going to put in a patch to ignore null function pointers instead of calling them, and see if my core dumps problems (and maybe also sporadic process hangs) go away. Joe Buehler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/