[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#25390: Segfault with sed 4.3
From: |
Norihiro Tanaka |
Subject: |
bug#25390: Segfault with sed 4.3 |
Date: |
Mon, 09 Jan 2017 23:04:05 +0900 |
On Sun, 8 Jan 2017 22:12:02 -0800
Paul Eggert <address@hidden> wrote:
> Norihiro Tanaka wrote:
> > I wrote two additional patches for dfa. First, derive number of
> > allocation from not argument but number of state in transition table
> > allocation. Second, melt down dfastate() into build_state(). Now, I
> > think that there do not have to be separated.
>
> Thanks, I installed those two patches into Gnulib.
Thanks.
> > I also wrote a simple test, but the issue are not always caused, as it
> > depends on state of memory. Should we rely to complate the test on
> > valgrind?
>
> Yes, I expect the 'sed' folks would prefer the test to use valgrind. You can
> look at testsuite/invalid-mb-seq-UMR.sh for an example of a test that does
> that.
Thanks, I updated the test. The new test uses valgrind.
0001-tests-new-test-for-dfa-crash-bug.patch
Description: Text document
- bug#25390: Segfault with sed 4.3, S. Gilles, 2017/01/08
- bug#25390: Segfault with sed 4.3, S. Gilles, 2017/01/08
- bug#25390: Segfault with sed 4.3, Assaf Gordon, 2017/01/08
- bug#25390: Segfault with sed 4.3, Paul Eggert, 2017/01/08
- bug#25390: Segfault with sed 4.3, S. Gilles, 2017/01/08
- bug#25390: Segfault with sed 4.3, Norihiro Tanaka, 2017/01/08
- bug#25390: Segfault with sed 4.3, Paul Eggert, 2017/01/09
- bug#25390: Segfault with sed 4.3,
Norihiro Tanaka <=
- bug#25390: Segfault with sed 4.3, Norihiro Tanaka, 2017/01/09
- bug#25390: Segfault with sed 4.3, Assaf Gordon, 2017/01/10
- bug#25390: Segfault with sed 4.3, Paul Eggert, 2017/01/10
- bug#25390: [Grep-devel] bug#25390: Segfault with sed 4.3, Jim Meyering, 2017/01/14
- bug#25390: Segfault with sed 4.3, Assaf Gordon, 2017/01/16