Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
From: "Hannu E K Nevalainen \(garbage mail\)" <garbage_collector AT telia DOT com>
To: <cygwin AT cygwin DOT com>
Subject: cygwin1.dll - debug version (RE: similar crash in mmap for 1.5.3-1)
Date: Tue, 9 Sep 2003 10:41:46 +0200
Message-ID: <NGBBLLIAMFLGJEOAJCCEMEMJDDAA.garbage_collector@telia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
In-Reply-To: <20030908234203.GA4227@redhat.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> Of Christopher Faylor

<SNIP>
> ... You can't get a reliable crash dump
> from a stripped DLL, which cygwin1.dll is, of course.  I can't believe
> that this has to be a FAQ entry but apparently it does.
>
> If you want to help with a back trace, you have to build your own version
> of the DLL with debugging symbols.

Idea, to help debug things like the above:

 Alt 1) Make an _unstripped_ cygwin1.dll available in a package named
        "cygwin-DEBUG-dll" or some such. Also make it be "TEST/Exp" forever.
 Alt 2) Have an unstripped cygwin1-DEBUG.dll added to the basic package,
        add a simple "cygswapdll" utility.

Is this a Good or Bad idea?

/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
--END OF MESSAGE--


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