X-Spam-Check-By: sourceware.org
Date: Mon, 9 Jan 2006 12:25:01 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: debugging cygwin
Message-ID: <20060109172501.GD19891@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <43C26C27 DOT 1070807 AT juno DOT nrl DOT navy DOT mil> <Pine DOT GSO DOT 4 DOT 63 DOT 0601090904471 DOT 20978 AT slinky DOT cs DOT nyu DOT edu> <43C29170 DOT 6050604 AT juno DOT nrl DOT navy DOT mil>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43C29170.6050604@juno.nrl.navy.mil>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Mon, Jan 09, 2006 at 11:38:08AM -0500, Ken Senior wrote:
>Ok, so Igor's directions seem to conflict with the FAQ #15 about
>whether or not cygwin services must be halted.  Can someone clarify
>that.

The FAQ is correct.  You need to stop all running services when you
replace the DLL.

>In any case, after renaming the snapshot DLLs (from both 1/7 and 1/8)
>to /bin/cygwin1.dll, I find that no cygwin process will launch, not
>even the bash window.  Replacing the old cygwin1.dll back reverts
>things to working again.  Can anyone suggest a a more "stable" snapshot
>one might use for debugging purposes?

Lets take a step back, please.

The snapshots do work and you can debug with them.  You are probably
doing something wrong when you unpack and copy the dll.  You should be
copying both the dll and the dbg file to a temporary area and bunzipping
them.  Then you may need to make sure that the DLL has executable
permissions.

So, the steps should be something like this (this is just an example, I
include it only for reference):

  c:\>mkdir tmp
  c:\>cd tmp
  c:\tmp>c:\cygwin\bin\wget http://cygwin.com/snapshots/cygwin1-20060109.dll.bz2
  c:\tmp>c:\cygwin\bin\wget http://cygwin.com/snapshots/cygwin1-20060109.dbg.bz2
  c:\tmp>c:\cygwin\bin\bunzip2 cygwin1-20060109.*
  c:\tmp>c:\cygwin\bin\chmod a+x cygwin1-20060109.*
  c:\tmp>copy c:\cygwin\bin\cygwin1.dll c:\cygwin\bin\cygwin1.dll.saf
  c:\tmp>ren cygwin1-20060109.dll cygwin1.dll
  c:\tmp>ren cygwin1-20060109.dbg cygwin1.dbg
  c:\tmp>copy cygwin1.d* c:\cygwin\bin

Btw, your next consternation point will probably come when you discover
that the .dbg file just provides the debugging symbols for the cygwin
DLL.  You are going to need the cygwin DLL sources if you want to do any
useful debugging.  And, unless you set up the sources in exactly the
same way as I did when I created the snapshot, you'll probably have to
investigate the gdb "directory" command.

There is a file in the cygwin source directory called "how-to-debug-cygwin.txt"
which might be instructive.

Oh, and, unless you really know what you're doing, you can't have two
versions of cygwin on your system at the same time.  You need to replace
the one in /bin .

cgf


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