On 2017-01-08T12:49:42-0800, Paul Eggert wrote:
> Assaf Gordon wrote:
> > The immediate cause is somewhere in gnulib's DFA module.
>
> The bug was introduced in Gnulib, in commit
> 403adf1b40897ba108075008c10bd38d937e1539 dated 2016-11-25 and labeled "dfa:
> addition of new state on demand". It's
* lib/getprogname.c (getprogname) [__sgi]:
Don't dump core if malloc returns NULL.
---
ChangeLog | 4
lib/getprogname.c | 7 +--
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 79475df..0d60422 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1
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 th
On Sun, 8 Jan 2017 12:49:42 -0800
Paul Eggert wrote:
> Assaf Gordon wrote:
> > The immediate cause is somewhere in gnulib's DFA module.
>
> The bug was introduced in Gnulib, in commit
> 403adf1b40897ba108075008c10bd38d937e1539
> dated 2016-11-25 and labeled "dfa: addition of new state on deman
Assaf Gordon wrote:
The immediate cause is somewhere in gnulib's DFA module.
The bug was introduced in Gnulib, in commit
403adf1b40897ba108075008c10bd38d937e1539 dated 2016-11-25 and labeled "dfa:
addition of new state on demand". It's not a bug that grep runs into, since grep
doesn't use th
Hello,
> On Jan 8, 2017, at 00:31, S. Gilles wrote:
>
>> I have a reliable segfault with (vanilla) sed 4.3 which does not appear
>> on (vanilla) 4.2.2.
Thank you for the report!
I can confirm the segfault is reproducible.
The immediate cause is somewhere in gnulib's DFA module.
A shorter examp
