SIGQUIT reported as SIGSEGV

[Daniel R. Grayson]

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@gmail.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