[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Crash recovery strategies
From: |
Eli Zaretskii |
Subject: |
Re: Crash recovery strategies |
Date: |
Mon, 04 Jan 2016 17:33:31 +0200 |
> 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.
- Crash recovery strategies (was: Dynamic modules: MODULE_HANDLE_SIGNALS etc.), (continued)
- Crash recovery strategies (was: Dynamic modules: MODULE_HANDLE_SIGNALS etc.), 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, Daniel Colascione, 2016/01/03
- Re: Crash recovery strategies, John Wiegley, 2016/01/03
- 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 <=
- Re: Crash recovery strategies, Daniel Colascione, 2016/01/04
- 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