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 From: Chris Faylor Date: Sun, 2 May 1999 19:12:39 -0400 To: Mumit Khan Cc: Egor Duda , cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: gdb "attach" and sharing thread info between processes Message-ID: <19990502191239.A716@cygnus.com> References: <7853 DOT 990501 AT logos-m DOT ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Mumit Khan on Sun, May 02, 1999 at 01:37:52PM -0500 On Sun, May 02, 1999 at 01:37:52PM -0500, Mumit Khan wrote: >On Sat, 1 May 1999, Egor Duda wrote: >> April, 30 1999, Chris Faylor 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. I agree. We'll also be fielding all sorts of confused comments from users if this is the default. How about `set CYGWIN=error_start=/usr/bin/gdb'? -chris