[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 18:02:50 +0200 |
> Cc: address@hidden, address@hidden
> From: Daniel Colascione <address@hidden>
> Date: Mon, 4 Jan 2016 07:34:24 -0800
>
> > 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.
The guard page is usually one or 2 pages, which is enough for most
uses of printf.
> And you continue to ignore the existence of the alternate signal
> stack.
No, I don't.
- 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, 2016/01/04
- Re: Crash recovery strategies,
Eli Zaretskii <=
- 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
- Re: Sending automatic crash reports to the FSF, Daniel Colascione, 2016/01/03