This is the mail archive of the
mailing list for the Cygwin project.
Re: 'bison' error, possibly installation related
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Daniel Edwards <ded at micromuse dot com>
- Cc: cygwin at cygwin dot com
- Date: Wed, 15 Oct 2003 11:03:04 -0400 (EDT)
- Subject: Re: 'bison' error, possibly installation related
- References: <email@example.com>
- Reply-to: cygwin at cygwin dot com
On Wed, 15 Oct 2003, Daniel Edwards wrote:
> I'm getting the following error when i'm running the following bison
> bison -yd -r all -p _NPropMgr prop_parser.y
> Signal 6
> *** Error code 134
> However, I've recently moved the cygwin installation and remounted and I
> think this is the real problem as I can make the problem go away if i
> recreate a cygwin installation from scratch, but the environment i'm working
> in isn't going to be able to support that.
> I need to know more about the error so that i can resolve it. I've been
> unable to find out anything so far. I'm assuming that Signal 6 is sigalrm.
> I'd like to know how i could find out more about error code 134, or what
> bison is struggling with that causes this issue.
When a subprocess dies with a signal, its exit status is 128+SIG, where
SIG is the numeric value of the signal. So, 134 is just telling you that
signal 6 (SIGALRM) has been received. No new info.
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html