X-Spam-Check-By: sourceware.org
Message-ID: <441D08AD.7CB8C98@dessent.net>
Date: Sat, 18 Mar 2006 23:30:53 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: =?iso-8859-1?Q?=CA=C0=D1=E5=20=CD=F5?= <wsycqyz AT hotmail DOT com>,
   cygwin AT cygwin DOT com
Subject: Re: About cygwin1.dll
References: <BAY113-F9CCC4DB92E517A0036CFDA3DA0 AT phx DOT gbl>
Content-Type: text/plain; charset=iso-8859-1
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k2J7V7KJ025223


Please post to the mailing list instead of sending email to me
directly.  By doing this you help everyone because there may be others
that will benefit, and the thread will be archived.

"ÊÀÑå Íõ" wrote:

>   I've read your article"[patch] fix spurious SIGSEGV faults under Cygwin",
> it's so helpful for me to understand the problem "Program received signal
> SIGSEGV, Segmentation fault.0x610af8b8 in pthread_key_create..."
>   But I am new for linux, and I don't how to use your attached patch in the
> article.

You shouldn't use my patch.  It's obsolete, and the problem is already
fixed in a better way by changes made by Christopher Faylor.  These
fixes are already checked in to CVS so just build from current sources
and you will get the fix.

>   Could you please send me the problem-solved version of cygwin1.dll
> directly, or send me some link about how to use your patch?

The problem is not in cygwin1.dll, it is in a lack of communication
between the DLL and gdb.  You need to build both from CVS in order to
get the fix.  For the cygwin side you can just use a daily snapshot. 
For gdb you will have to build it from CVS or wait for an updated
package.

Please remember that these SIGSEGVs you are seeing are not real
segmentation violations, they are just a consequence of how error
checking is done in the DLL.  They are expected to happen, and when they
occur a fault handler in the cygwin DLL is in place to catch them and
handle the situation cleanly.  Consequently you can always just type "c"
or "continue" at the gdb prompt and everything will resume as usual. 
That is all that the above mentioned changes do -- make gdb ignore the
fault and continue.

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/