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
X-Authentication-Warning: modi.xraylith.wisc.edu: khan owned process doing -bs
Date: Sun, 2 May 1999 13:37:52 -0500 (CDT)
From: Mumit Khan <khan AT xraylith DOT wisc DOT edu>
To: Egor Duda <deo AT logos-m DOT ru>
cc: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: gdb "attach" and sharing thread info between processes
In-Reply-To: <7853.990501@logos-m.ru>
Message-ID: <Pine.SUN.3.93.990502133602.20497C-100000@modi.xraylith.wisc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sat, 1 May 1999, Egor Duda wrote:

> Hi!
> 
> April, 30 1999, Chris Faylor <cgf AT cygnus DOT com> wrote:
> 
> >>I'm   also  planning  to  make  a  patch  to winsup, which would allow
> >>to  handle exceptions  by  starting  debugger.  i  think  it  would be
> >>acceptable  substitution  for  core  files  functionality. What do you
> >>think about usefulness of such patch?
> 
> CF> It sounds like a good idea as long as it doesn't add too much bloat to the
> CF> DLL.
> 
> So, here it goes. It was made against Snapshot-1999/04/10. It's rather
> gdb-centric, but i don't think any other debugger can handle gcc's
> debug info anyway.
> 

This can be quite useful at times; however I find that I'd rather not have 
it on by default, or in other words, it should be configurable via either
env variable (my preference) or by a registry entry.

Regards,
Mumit