Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Wed, 4 Jul 2001 12:25:50 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: problem with 20010701 snapshot
Message-ID: <20010704122550.A8007@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <5564-Wed04Jul2001160307+0100-starksb AT ebi DOT ac DOT uk> <20010704114305 DOT A7053 AT redhat DOT com> <1471-Wed04Jul2001172358+0100-starksb AT ebi DOT ac DOT uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <1471-Wed04Jul2001172358+0100-starksb@ebi.ac.uk>; from starksb@ebi.ac.uk on Wed, Jul 04, 2001 at 05:23:58PM +0100

On Wed, Jul 04, 2001 at 05:23:58PM +0100, David Starks-Browning wrote:
>On Wednesday 4 Jul 01, Christopher Faylor writes:
>> In general, stack dumps are meaningless unless you have a debugging version
>> of the DLL with which you can match addresses and symbols.
>>
>> The best way to track this down is to build your own version of the DLL and
>> then use either gdb or addr2line to figure out where the DLL is dying.
>
>OK, when I return in a couple of weeks.  I've always wanted to build
>my own DLL anyway.
>
>Wouldn't it be sensible to distribute debugging versions of the DLL
>with the snapshots?

Yes, but they make the snapshots a lot bigger.

Corinna and I talked about distributing a "sym" file that cygcheck could
interpret a while ago.  That was actually what caused me to add bz2 support
to setup.exe.

I wanted to play with getting bz2lib incorporated into the winsup
directory and thought that it would be a good proof of concept to get it
into setup.exe.

Now that I have that, we can distribute a bzipped sym file along with the
snapshots.  As soon as I round my tuit.

cgf