[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Failing test case 67 Fatal errors but M4 continues producing output

From: Joel E. Denny
Subject: Re: Failing test case 67 Fatal errors but M4 continues producing output
Date: Sun, 11 Apr 2010 14:40:16 -0400 (EDT)
User-agent: Alpine 1.00 (DEB 882 2007-12-20)

On Sun, 11 Apr 2010, Bruno Haible wrote:

> The code in bison-2.4.2/src/output.c looks fine.

Thanks for confirming.

> Can you help reproducing or debugging it, with just 2 executables: bison
> and m4? (I.e. give a "how to reproduce" that does not involve bison's
> testsuite? I'm not inclined to look into a 3 MB large machine generated
> shell script.)

Because I do not have access to the affected platform, I can only explain 
the actions that the failing test group performs.  Petr, can you please 
confirm that the following instructions produce the problem for you? 
Recall that there may be a race condition, so run bison many times if it 
does not produce the problem at first.  Also, please remind us exactly 
which platform exhibits the problem.

First, create a file named gen-skel.pl with the following contents:

use warnings;
use strict;
my $M4 = "m4";
my $DNL = "d"."nl";
print "${M4}_divert_push(0)$DNL\n";
print '@output(@,@)', "\n";
(print "garbage"x10, "\n") for (1..1000);
print "${M4}_divert_pop(0)\n";

Run: perl gen-skel.pl > skel.c

Create a file named input.y with the following contents:

%skeleton "./skel.c"
start: ;

Run: bison-2.4.2/tests/bison input.y

The output should look like:

  input.y: fatal error: too many arguments for @output directive in skeleton

On the affected platform, it also contains something like:

  /usr/bin/m4:./skel.c:175: ERROR: copying inserted file: Broken pipe
  /usr/bin/m4: write error

reply via email to

[Prev in Thread] Current Thread [Next in Thread]