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: <4317D378.236A02D9@dessent.net>
Date: Thu, 01 Sep 2005 21:22:16 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Segfault in Cactid
References: <loom DOT 20050902T024037-588 AT post DOT gmane DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Larry Adams wrote:

> So my questions are: How do I trace the memory location above to a known system
> call using gdb?  When, I attach to my hung process, what should I be doing to
> determine the calling/offending function.

Build a cygwin1.dll with debug symbols and then use addr2line.  Or use
strace.  At the very least you should try the latest snapshot to see if
it fixes your problem.

The fact that you get that popup is a little puzzling.  That popup is
the result of an SEH exception not being handled by the process and
falling through to the system default handler.  But Cygwin installs its
own SEH handlers so that it can convert those sort of exceptions into
"signal 11" without the popup.  Normally you would not get a popup and
it would terminate as on unix with a segmentation fault message and
stackdump.  But I guess if something internal to Cygwin is getting
corrupted then all bets are off.

Brian

--
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/