Re: SVN Revision 1914 and higher
- Posted by bernie Apr 11, 2009
- 959 views
Just a warning, 1914 and higher are broke. Work is being done to fix it, but in the mean time, do not do a svn up or you will be sorry. It will compile but result in an unusable interpreter/translator/backend. Stick with your current versions until you hear more here that SVN is functional again.
Jeremy
Jeremy:
I had some code that worked on any binary prior to the change to interpreter's new names.
Any binaries after the name changed; exhibited the failure.
I am using dynamic inline assembler that is built into my code so I had no way to create an example to show the failure.
It is a strtok function that fails to parse anything and returns a result of zero on the first call.
I think that the change back to only managed memory introduced some kind of memory problem because the strtok depends on allocated buffer to be persistent.
I didn't report it because I had no way of proving it. So I decided to wait because I knew the error would eventually show up under other circumstances.
So my suggestion is to go back to the SVN when the names were changed and start looking there.
