Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Sun, 27 Jun 1999 23:47:44 -0400
Message-Id: <199906280347.XAA01243@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: khan AT xraylith DOT wisc DOT EDU
CC: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <199906280336.WAA24373@mercury.xraylith.wisc.edu> (message from
	Mumit Khan on Sun, 27 Jun 1999 22:36:31 -0500)
Subject: Re: running two independent Cygwin DLLs?
References:  <199906280336 DOT WAA24373 AT mercury DOT xraylith DOT wisc DOT edu>


> How do you guys do it?

printf and strace are popular ;-)

Seriously, I have a batch file that copies a given cygwin dll to all
the places it resides on my hard drive, and I have a cache of known
good dlls to restore from.  When I'm debugging dll problems, the first
thing to do is get out of bash and make sure that the *only* cygwin
program you're running is the one you're debugging (and/or gdb).

Or, I just make sure the debug dll is in the current directory with my
test program.