Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Mon, 8 Oct 2001 15:06:44 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Perl 5.7.2
Message-ID: <20011008150644.C19660@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3BC1CF2E DOT 7177 DOT 33050F17 AT localhost> <3BC1B8C0 DOT C1E58D08 AT rowman DOT com> <20011008115635 DOT A18826 AT redhat DOT com> <5 DOT 0 DOT 2 DOT 1 DOT 2 DOT 20011008123354 DOT 00b186b0 AT sen-mail DOT gtri DOT gatech DOT edu> <upu7yoxmz DOT fsf AT yandex DOT ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <upu7yoxmz.fsf@yandex.ru>
User-Agent: Mutt/1.3.21i

On Mon, Oct 08, 2001 at 09:21:56PM +0400, Roman Belenov wrote:
>Ok, let's stop quarreling and return to the facts. On my system
>debugging with cygwin-1.3.3-2 is also not possible - debuggee receives
>unknown signals before reaching main(). I reproduced it on the empty
>program (after encountering on the real one). It is indeed a
>regression - downgrading to cygwin-1.3.2-1 makes debugging fine. There
>were several other messages stating that debugging doesn't work with
>1.3.3 and changing to 1.3.2 fixes the problem. So it seems that it is
>in fact a bug. It doesn't mean that cygwin developers must start
>working on it immediately and I (as, I guess, other bug reporters)
>don't expect it, but it should be registered as a known bug and bug
>reports should be treated like efforts to provide help to someone who
>will eventually work on fixing it.

I guess what I find ironic here is the fact that we are talking about
a *debugger* not working and there have been debugging methods posted
which talk about how the problem could be *debugged*.

However, no one seems interested in *debugging* the problem themselves.

I'll ask again if anyone who was having the problem still has the problem
with the latest cygwin snapshot.  That's a pretty obvious thing to try
but it doesn't seem like anyone has tried it yet.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/