Re: SIGQUIT reported as SIGSEGV

2013-04-30 Thread Christopher Faylor
On Tue, Apr 30, 2013 at 07:11:19AM -0500, Daniel R. Grayson wrote: >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 Th

Re: SIGQUIT reported as SIGSEGV

2013-04-30 Thread 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 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: >>>

Re: SIGQUIT reported as SIGSEGV

2013-04-30 Thread jojelino
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 dumpe

Re: SIGQUIT reported as SIGSEGV

2013-04-30 Thread Helmut Karlowski
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