delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/10/12/13:02:37

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <20041012165842.37385.qmail@web60802.mail.yahoo.com>
Date: Tue, 12 Oct 2004 09:58:42 -0700 (PDT)
From: Peter Xiaochuan Huang <xchuang AT yahoo DOT com>
Subject: gcc exception handling
To: cygwin AT cygwin DOT com
MIME-Version: 1.0

I don't know if this a known issue. But I encounter
this problem when using gcc 3.3.3 on cygwin. The code
similar to below core dumps me.

   try {
      obj->dothis();
   }
    catch ( myexception& e)
    {
        return true;
     }

It core dumps on the return statement in gdb. But when
I make a simplified test including only above code,
the core dump doesn't happen any more. My program that
gets core dumped links pthread and uses mutex.
Actually the return statement should invoke stack
unwinding that will do mutex locking and unlocking.
Though I don't know if that is related or not.

Anybody else has similar problem ? Any suggestion?

-Peter X Huang


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019