[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Crash recovery strategies
From: |
Daniel Colascione |
Subject: |
Re: Crash recovery strategies |
Date: |
Mon, 4 Jan 2016 07:34:24 -0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 |
On 01/04/2016 07:33 AM, Eli Zaretskii wrote:
>> From: Daniel Colascione <address@hidden>
>> Date: Sun, 3 Jan 2016 14:55:26 -0800
>>
>> The code that bothers me is the code that longjmps *out* of the sigsegv
>> handler that catches stack overflow. The handler being there is fine.
>> Under my proposed scheme, we won't longjmp out of the handler unless the
>> user tells us to do that.
>
> You won't be able to do anything except call printf, without jumping
> out of the handler. The stack space left after stack overflow is too
> small for anything fancier. You will almost certainly crash, that's
> all.
There's no guarantee that you can even call printf. And you continue to
ignore the existence of the alternate signal stack.
>
signature.asc
Description: OpenPGP digital signature
- Re: Crash recovery strategies, (continued)
- Re: Crash recovery strategies, John Wiegley, 2016/01/03
- Re: Crash recovery strategies, Daniel Colascione, 2016/01/03
- Re: Crash recovery strategies, John Wiegley, 2016/01/03
- Re: Crash recovery strategies, Eli Zaretskii, 2016/01/04
- Re: Crash recovery strategies, Daniel Colascione, 2016/01/04
- Re: Crash recovery strategies, Eli Zaretskii, 2016/01/04
- Re: Crash recovery strategies,
Daniel Colascione <=
- Re: Crash recovery strategies, Eli Zaretskii, 2016/01/04
- Re: Crash recovery strategies, Paul Eggert, 2016/01/03
- Re: Crash recovery strategies, Daniel Colascione, 2016/01/03
- Re: Crash recovery strategies, John Wiegley, 2016/01/03
- Re: Crash recovery strategies, Paul Eggert, 2016/01/03
- Re: Crash recovery strategies, John Wiegley, 2016/01/03
- Re: Crash recovery strategies, Daniel Colascione, 2016/01/03
- Sending automatic crash reports to the FSF (was: Crash recovery strategies), John Wiegley, 2016/01/03
- Re: Sending automatic crash reports to the FSF, Daniel Colascione, 2016/01/03
- Re: Sending automatic crash reports to the FSF, John Wiegley, 2016/01/03