X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=Fb
	hLF+EptI20R6sjLQ9RhXTkLuZRxnyD/fuaBdK8pWNgdAVSce4P3fZY53V3uZrKia
	d0dwTLCPUzPDMQmsuizIskKsbarrF3IYohtbtFYlp4KRFq12PnXd1cRuD2s2GyBL
	RnGCJtt0cxJyIrNdIi/4cxTUlrkd/m+iLlDjTXoWw=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=srzvkD8K
	7FRtVsoJ/IngtWBDlAM=; b=vHLheKKWfBncCT/igkuhZKN/EDjLqAxecVABkNC6
	NhaROgFMTA5QpreNdYHyjoIXkJUE/YYzJmEZNu+Ai2wFtrjyiS6pQRvq5/G6zujs
	2qXmKwN1RlLQgNgBwQhZtl9CZSZB1bIrOXJl/Btl0e6gCsObIfhX/etA4+LKammA
	uhQ=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status:	No, score=-3.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1
MIME-Version:	1.0
X-Received:	by 10.194.133.130 with SMTP id pc2mr22374710wjb.35.1367332979551; Tue, 30 Apr 2013 07:42:59 -0700 (PDT)
In-Reply-To:	<klojpi$hhv$1@ger.gmane.org>
References:	<CABWu70G4kLJioA4+E3usOZ_TZpRT1iN5v0ZuAFKy3UyqSHt=jw AT mail DOT gmail DOT com> <op DOT wwctdg0wofd6j1 AT nebbiolo DOT upc DOT de> <klojpi$hhv$1 AT ger DOT gmane DOT org>
Date:	Tue, 30 Apr 2013 09:42:59 -0500
Message-ID:	<CABWu70HqL3BGQ86Kv4fzNsAA20uVTQcCeUboCkjsHfL4JSGCOA@mail.gmail.com>
Subject:	Re: SIGQUIT reported as SIGSEGV
From:	"Daniel R. Grayson" <danielrichardgrayson AT gmail DOT com>
To:	cygwin AT cygwin DOT com

The backtrace routine could set up a handler for SEGV and give up silently.

On Tue, Apr 30, 2013 at 9:17 AM, jojelino <jojelino AT gmail DOT com> wrote:
> On 2013-04-30 PM 9:37, Helmut Karlowski wrote:
>>
>> Daniel R. Grayson, 30.04.2013 14:11:19:
>>
>>> SIGQUIT is erroneously delivered as SIGSEGV in this circumstance:
>>>
>>>     $ sleep 1000 &
>>>     [1] 9148
>>>     $ kill -QUIT %1
>>>     $    < press return if necessary here >
>>>     [1]+  Segmentation fault      (core dumped) sleep 1000
>>
>>
>> It's sleep.exe that crashes, the report is correct.
>>
>> Stack trace:
>> Frame     Function  Args
>> 0022AAC8  7C80A115  (00000003, 0022AB2C, 00000000, FFFFFFFF)
>>
> --- Process 7188, exception C0000005 at 6102F813
> sh-4.1$ addr2line -e /bin/cygwin1.dbg
> 6102F813
> /netrel/src/cygwin-snapshot-20130409-1/winsup/cygwin/exceptions.cc:252
>
> It's long-standing bug during stack backtrace in cygwin. if any frame has
> used ebp for purposes other than frame pointer. which is mostly the case.
> --
> Regards.
>
>
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -