Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Tue, 17 Oct 2000 12:05:32 -0400
To:	cygwin AT sources DOT redhat DOT com
Cc:	jik AT curl DOT com
Subject:	Re: rxvt SEGV (Win98, 1.1.5s/2000-10-08)
Message-ID:	<20001017120532.B9581@cygnus.com>
Reply-To:	cygwin AT sources DOT redhat DOT com
Mail-Followup-To:	cygwin AT sources DOT redhat DOT com, jik AT curl DOT com
References:	<20001017152857 DOT 19990 DOT qmail AT web114 DOT yahoomail DOT com> <20001017153855 DOT 2548 DOT qmail AT lizard DOT curl DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.6i
In-Reply-To:	<20001017153855.2548.qmail@lizard.curl.com>; from jik@curl.com on Tue, Oct 17, 2000 at 11:38:55AM -0400

On Tue, Oct 17, 2000 at 11:38:55AM -0400, Jonathan Kamens wrote:
>>  Date: Tue, 17 Oct 2000 08:28:57 -0700 (PDT)
>>  From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
>>  
>>  The best way to help is to get the CVS source and build it (it
>>  takes ~30 minutes on my PII Compaq armada to do the make).  The
>>  new-cygwin1.dll that is produced contains debugging symbols and is
>>  about 3.5M large.  You'll copy this to the cygwin1.dll in the bin
>>  directory.  Then using common debugging methods figure out what's
>>  wrong.  If you use strace be sure to use the most recent version as
>>  some bug fixes to strace itself have occurred.
>
>Surely you're not asserting that "using common debugging methods [to]
>figure out what's wrong" within the complex internals of Cygwin is an
>easy task.

It can be.  When you run the program under a debugger, you should be
able to see the instruction causing the (I assume) SIGSEGV.  That
should provide an incredible clue.

>In fact, we have a developer here who did that a couple years ago and
>sent a whole slew of fixes to the Cygwin maintainers to various race
>conditions which manifested themselves on MP machines.  His opinion is
>that the Cygwin developers have always been a bit sloppy about
>handling the issues that arise on MP machines.  He has also asserted
>that debugging Cygwin internals is very hard, certainly not something
>that can be done easily "using common debugging methods."

I don't recall any such patches.  I'm usually very grateful for patches
of any kind.

I do take great exception to the "sloppy" allegation.  You are actually
trying to work with us right?  It doesn't take a PHD in psychology to
understand that this is an incredibly poor way to ask for help.

As I previously indicated, I use an SMP machine and have done so since I
started working on Cygwin.  I am painfully aware of MP issues.

>Short of becoming a Cygwin expert, is there anything I can do to make
>it possible for the people who are already Cygwin experts to debug
>this problem?

The details were in my previous email.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -