[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A bit more info about hanging bison on tru64 5.1b
From: |
Didier Godefroy |
Subject: |
Re: A bit more info about hanging bison on tru64 5.1b |
Date: |
Thu, 25 Jun 2009 13:35:39 +0200 |
User-agent: |
Microsoft-Entourage/12.19.0.090515 |
on 6/25/09 1:09 PM, Akim Demaille at address@hidden uttered the
following:
>> src/bison: subsidiary program `/usr/bin/gm4' failed
>
> This is precious information: it is not Bison but M4 that hangs.
> Could you give me the result of /usr/bin/gm4 --version please?
m4 (GNU M4) 1.4.9
That's odd, because I don't remember having any issues during m4's test
suite, it passed and didn't seem to give any troubles.
Besides, sendmail makes extensive use of m4 during install and it worked
fine.
>> And the hang still occurs.
>
> Huh? So you are saying that
>
> cat >test-1.y <<EOF
> %token <integer> INT;
> %type <integer> a b c d e f g h i j k l;
> %destructor { destroy ($$); } INT a b c d e f g h i j k l;
> %%
> start:
> 'a' a { $2; } | 'b' b { $2; } | 'c' c { $2; } | 'd' d { $2; }
> | 'e' e { $2; } | 'f' f { $2; } | 'g' g { $2; } | 'h' h { $2; }
> | 'i' i { $2; } | 'j' j { $2; } | 'k' k { $2; } | 'l' l { $2; }
> ;
>
> a: INT|;
> b: INT|;
> c: INT|;
> d: INT|;
> e: INT|;
> f: INT|;
> g: INT|;
> h: INT|;
> i: INT|;
> j: INT|;
> k: INT|;
> l: INT|;
> EOF
> ./tests/bison test-1.y </dev/null
>
> hangs?
Yes it does:
503268 root 48 0 4968K 106K run 0:30 99.70% bison
I have to kill it or it just hangs there that way. And also on gm4
> What about
>
> cat >test-2.y <<EOF
> %token <integer> INT;
> %type <integer> a;
> %destructor { destroy ($$); } INT a;
> %%
> start:
> 'a' a { $2; };
>
> a: INT;
> EOF
> ./tests/bison test-2.y </dev/null
Yes, same thing.
> Using the smallest test that fails, could you please run
>
> ./tests/bison --trace=m4 test-<N>.y </dev/null 2>m4.log
>
> m4.log will probably be extremely long. Either it will "end" on
> single command, or it will repeat some lines over and over. We don't
> need the whole log, only the end matters, particularly the loop body,
> if it does loop.
./tests/bison --trace=m4 test-2.y </dev/null 2>m4.log
Hangs and the m4.log is actually quite short:
test-2.y:6.4-14: warning: unused value: $2
That's all there is in there.
And when I kill the hung process, this gets added:
/usr/local/bison/src/src/bison: subsidiary program `/usr/bin/gm4' failed
I will try with the tru64 m4 now...
--
Didier Godefroy
mailto:address@hidden
Support anti-Spam legislation.
Join the fight http://www.cauce.org/