I installed the files from bison-1.35-1-bin.zip in my usual collection of directories, which has been fine for several other GnuWin32 distributions. When I try to run it with more than one (and sometimes with just one) option, it pops up an Application Error alert: "The instruction at [blah blah hex address] referenced memory at [blah blah other hex address]. The memory could not be "read".
And then sometimes, the ones that "work" won't work any more, as if running bison is leaving a persistent bad condition somewhere. And it seems to be a really persistent condition, because if I close the command window and open up a new one, I get similar results.
Help?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I installed the files from bison-1.35-1-bin.zip in my usual collection of directories, which has been fine for several other GnuWin32 distributions. When I try to run it with more than one (and sometimes with just one) option, it pops up an Application Error alert: "The instruction at [blah blah hex address] referenced memory at [blah blah other hex address]. The memory could not be "read".
Works:
bison myfile.y
bison -ptec myfile.y
bison -d myfile.y
Doesn't work:
bison --defines --name-prefix=my myfile.y
bison --name-prefix=my myfile.y
bison -d -pmy myfile.y
And then sometimes, the ones that "work" won't work any more, as if running bison is leaving a persistent bad condition somewhere. And it seems to be a really persistent condition, because if I close the command window and open up a new one, I get similar results.
Help?
On Windows-98 all your examples work fine. Could you post a small bison file that shows the behaviour you describe?