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
Message-Id: <199906280336.WAA24373@mercury.xraylith.wisc.edu>
To: Chris Faylor <cgf AT cygnus DOT com>
cc: dj AT delorie DOT com, cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: running two independent Cygwin DLLs? 
In-Reply-To: Your message of "Sun, 27 Jun 1999 23:08:39 EDT."
             <19990627230839 DOT A8904 AT cygnus DOT com> 
Date: Sun, 27 Jun 1999 22:36:31 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Chris and DJ,

Thanks for the useful discussion. I'm running it right now, but I'm
running into some debugging problems unfortunately. GDB seems to be
getting SIGTRAP in the child (which is using this new modified DLL),
but only at times. However, the linked program run just fine.

It's probably best to just find another machine and use that instead.
For once I regret getting rid windows from my laptop.

How do you guys do it? Keep in mind that I never work on a windows box,
so go slow please.

>
> My only request is:  Please!   Don't even think of advising anyone
> to do this at home.  It has great potential for problems and I really
> don't want to see people attempting this on the cygwin mailing list.
> My standard response to cygwin users has always been to keep only one
> version of the DLL on the system.  That is always the safest way to
> do things.

That's the reason I posted to the cygwin-dev list hoping that most people
here already know the dangers of playing with fire ;-)

Regards,
Mumit