[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nano-devel] solving a history bug in nano [patch]
From: |
alpha |
Subject: |
Re: [Nano-devel] solving a history bug in nano [patch] |
Date: |
Mon, 30 May 2016 09:51:49 -0600 |
On Mon, 30 May 2016 09:20:24 +0200
Benno Schulenberg <address@hidden> wrote:
> try instead of (size_t)-1 the values 100, 255, 32000, 65535. If
> none of those segfault, then at least we have a workaround: nobody
> is going to type sixty-five thousand characters to search for.
No one will ever need more than 640k of memory!
The value might be converted to a signed int somewhere inside find_history.
Perhaps use the largest value possible that can never be negative?
#define SIZE_T_HALF_MAX ((~(size_t)0)>>1)
- [Nano-devel] solving a history bug in nano [patch], Benno Schulenberg, 2016/05/29
- Re: [Nano-devel] solving a history bug in nano [patch], Tito, 2016/05/29
- Re: [Nano-devel] solving a history bug in nano [patch], Benno Schulenberg, 2016/05/29
- Re: [Nano-devel] solving a history bug in nano [patch], Tito, 2016/05/29
- Re: [Nano-devel] solving a history bug in nano [patch], Benno Schulenberg, 2016/05/29
- Re: [Nano-devel] solving a history bug in nano [patch], Tito, 2016/05/29
- Re: [Nano-devel] solving a history bug in nano [patch], Benno Schulenberg, 2016/05/30
- Re: [Nano-devel] solving a history bug in nano [patch], Tito, 2016/05/30
- Re: [Nano-devel] solving a history bug in nano [patch],
alpha <=
- Re: [Nano-devel] solving a history bug in nano [patch], Tito, 2016/05/30
- Re: [Nano-devel] solving a history bug in nano [patch], Benno Schulenberg, 2016/05/31
- Re: [Nano-devel] solving a history bug in nano [patch], Tito, 2016/05/31
- Re: [Nano-devel] solving a history bug in nano [patch], Benno Schulenberg, 2016/05/31
- Re: [Nano-devel] solving a history bug in nano [patch], Tito, 2016/05/31
- Re: [Nano-devel] solving a history bug in nano [patch], alpha, 2016/05/31
- Re: [Nano-devel] solving a history bug in nano [patch], Tito, 2016/05/31
- Re: [Nano-devel] solving a history bug in nano [patch], Tito, 2016/05/29