Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 17:23:58 +0100 Message-ID: <1471-Wed04Jul2001172358+0100-starksb@ebi.ac.uk> X-Mailer: emacs 20.7.1 (via feedmail 9-beta-7 I); VM 6.92 under Emacs 20.7.1 From: David Starks-Browning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: cygwin-developers AT cygwin DOT com Subject: Re: problem with 20010701 snapshot In-Reply-To: <20010704114305.A7053@redhat.com> References: <5564-Wed04Jul2001160307+0100-starksb AT ebi DOT ac DOT uk> <20010704114305 DOT A7053 AT redhat DOT com> 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? Thanks, David