GNU bug report logs - #25390
Segfault with sed 4.3

Previous Next

Full log

View this message in rfc822 format

From: Norihiro Tanaka <noritnk <at> kcn.ne.jp>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 25390 <at> debbugs.gnu.org, Assaf Gordon <assafgordon <at> gmail.com>, Gnulib bugs <bug-gnulib <at> gnu.org>, "S. Gilles" <sgilles <at> math.umd.edu>, GNU grep developers <grep-devel <at> gnu.org>
Subject: bug#25390: Segfault with sed 4.3
Date: Mon, 09 Jan 2017 23:04:05 +0900

[Message part 1 (text/plain, inline)]

On Sun, 8 Jan 2017 22:12:02 -0800
Paul Eggert <eggert <at> cs.ucla.edu> 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 (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.