On Thu, 2002-09-26 at 16:52, Ferguson, Neale wrote: > So are these messages important? > > MONO_PATH=/opt/mono/lib mint runtime/mcs.exe mono/tests/box.cs > > ** (process:19171): WARNING **: Using non-atomic functions!
This means that its faking the atomic increment/decrement etc functions with a spinlock, but they can still be accessed non-atomically if the variables are altered behind the back of the "atomic" functions. To shut this up you need to implement s390-specific atomic functions in atomic.h; there already are x86 and sparc versions there to crib from. > > ** (process:19171): WARNING **: System.IO.SeekOrigin has unknown value 0x14e > > ** (process:19171): WARNING **: System.IO.SeekOrigin has unknown value 0x14e > > ** (process:19171): WARNING **: System.IO.SeekOrigin has unknown value 0x14e > > ** (process:19171): WARNING **: System.IO.SeekOrigin has unknown value 0x14e > Compilation succeeded > ** (process:19171): WARNING **: System.IO.SeekOrigin has unknown value 0x15 These are showing up a real bug somewhere. The value you are passing to the Seek internal call in metadata/file-io.c is bogus. It could be because the value has been marshalled incorrectly. This particular symptom has shown up a lot - try searching bugzilla to see how it has been resolved before. http://bugzilla.ximian.com/show_bug.cgi?id=30035 seems to be the only one I can find and it doesnt give any details on the fix, unfortunately. You may be able to cross reference CVS commits though. - Dick _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
