Serialization in Mono

[Nikola Skoric]

I ran in Mono a program developed on .NET Framework 2.0 and it ran OK
until I tried to desirialize a object. There the program died abruptly
dumping this:

System.Argument OutOfRangeExcep tion: Value -859032199088540 0808 is
outside the valid range [0,3155378975999 999999].
Parameter name: ticks
at System.DateTime ..ctor (Int64 ticks) [0x00000]
at
System.Runtime. Serialization.F ormatters.Binar y.ObjectReader. ReadPrimitiv
eTypeValue (System.IO.Bina ryReader reader, System.Type type) [0x00000]
at
System.Runtime. Serialization.F ormatters.Binar y.ObjectReader. ReadValue
(System.IO.Bina ryReader reader, System.Object parentObject, Int64
parentObjectId, System.Runtime. Serialization.S erializationInf o info,
System.Type valueType, System.String fieldName,
System.Reflecti on.MemberInfo memberInfo, System.Int32[] indices)
[0x00000]
at
System.Runtime. Serialization.F ormatters.Binar y.ObjectReader. ReadObjectCo
ntent (System.IO.Bina ryReader reader,
System.Runtime. Serialization.F ormatters.Binar y.TypeMetadata metadata,
Int64 objectId, System.Object& objectInstance,
System.Runtime. Serialization.S erializationInf o& info) [0x00000]
at
System.Runtime. Serialization.F ormatters.Binar y.ObjectReader. ReadObjectIn
stance (System.IO.Bina ryReader reader, Boolean isRuntimeObject , Boolean
hasTypeInfo, System.Int64& objectId, System.Object& value,
System.Runtime. Serialization.S erializationInf o& info) [0x00000]
at
System.Runtime. Serialization.F ormatters.Binar y.ObjectReader. ReadObject
(BinaryElement element, System.IO.Binar yReader reader, System.Int64&
objectId, System.Object& value,
System.Runtime. Serialization.S erializationInf o& info) [0x00000]
at
System.Runtime. Serialization.F ormatters.Binar y.ObjectReader. ReadNextObje
ct (System.IO.Bina ryReader reader) [0x00000]
at
System.Runtime. Serialization.F ormatters.Binar y.ObjectReader. ReadObjectGr
aph (System.IO.Bina ryReader reader, Boolean readHeaders, System.Object&
result, System.Runtime. Remoting.Messag ing.Header[]& headers) [0x00000]
at
System.Runtime. Serialization.F ormatters.Binar y.BinaryFormatt er.NoCheckDe
serialize (System.IO.Stre am serializationSt ream,
System.Runtime. Remoting.Messag ing.HeaderHandl er handler) [0x00000]
at
System.Runtime. Serialization.F ormatters.Binar y.BinaryFormatt er.Deseriali
ze (System.IO.Stre am serializationSt ream) [0x00000]
at LanguageSystem. WordDisplay.ope nFileDialog1_Fi leOk (System.Object
sender, System.Componen tModel.CancelEv entArgs e) [0x00000]
at (wrapper delegate-invoke)
System.Multicas tDelegate:invok e_void_object_C ancelEventArgs
(object,System. ComponentModel. CancelEventArgs )
at System.Windows. Forms.FileDialo g.OnFileOk
(System.Compone ntModel.CancelE ventArgs e) [0x00000]
at System.Windows. Forms.FileDialo g.OnClickOpenSa veButton
(System.Object sender, System.EventArg s e) [0x00000]
at System.Windows. Forms.FileDialo g.OnForceDialog EndFileView
(System.Object sender, System.EventArg s e) [0x00000]
at (wrapper delegate-invoke)
System.Multicas tDelegate:invok e_void_object_E ventArgs
(object,System. EventArgs)
at System.Windows. Forms.MWFFileVi ew.OnDoubleClic k (System.EventAr gs e)
[0x00000]
at System.Windows. Forms.ListView+ ItemControl.Ite msMouseDown
(System.Object sender, System.Windows. Forms.MouseEven tArgs me) [0x00000]
at (wrapper delegate-invoke)
System.Multicas tDelegate:invok e_void_object_M ouseEventArgs
(object,System. Windows.Forms.M ouseEventArgs)
at System.Windows. Forms.Control.O nMouseDown
(System.Windows .Forms.MouseEve ntArgs e) [0x00000]
at System.Windows. Forms.Control.W ndProc (System.Windows .Forms.Message&
m) [0x00000]
at System.Windows. Forms.ListView+ ItemControl.Wnd Proc
(System.Windows .Forms.Message& m) [0x00000]
at System.Windows. Forms.Control+C ontrolNativeWin dow.WndProc
(System.Windows .Forms.Message& m) [0x00000]
at System.Windows. Forms.NativeWin dow.WndProc (IntPtr hWnd, Msg msg,
IntPtr wParam, IntPtr lParam) [0x00000]

I've been trying to figure out what went wrong, but I can't see it. Any
ideas?

--
"Now the storm has passed over me
I'm left to drift on a dead calm sea
And watch her forever through the cracks in the beams
Nailed across the doorways of the bedrooms of my dreams"

[rossum]

On Tue, 15 May 2007 17:27:58 +0200, Nikola Skoric <ni*******@net4 u.hr>
wrote:

Look at the first error in the hierarchy - all the others just tell
you that one of their subroutines failed.

>System.Argumen tOutOfRangeExce ption: Value -859032199088540 0808 is
outside the valid range [0,3155378975999 999999].
Parameter name: ticks
at System.DateTime ..ctor (Int64 ticks) [0x00000]

It looks llike you have an invalid number of ticks where the app is
trying to reconstruct a DateTime using a constructor with a single
Int64 parameter of the number of ticks.

Check for file corruption, or for an improperly constructed file.

rossum

[Peter Duniho]

On Tue, 15 May 2007 08:27:58 -0700, Nikola Skoric <ni*******@net4 u.hr>
wrote:

I ran in Mono a program developed on .NET Framework 2.0 and it ran OK
until I tried to desirialize a object. There the program died abruptly
dumping this:

System.Argument OutOfRangeExcep tion: Value -859032199088540 0808 is
outside the valid range [0,3155378975999 999999].
Parameter name: ticks
at System.DateTime ..ctor (Int64 ticks) [0x00000]
at
System.Runtime. Serialization.F ormatters.Binar y.ObjectReader. ReadPrimitiv
eTypeValue (System.IO.Bina ryReader reader, System.Type type) [0x00000]
[...]

Well, at first glance it appears to be a signed/unsigned mismatch. But, I
suppose it's also possible that the exception output is incorrectly
formatting the input value and that it's simply a genuine "your number is
too big" exception.

What I would do is take the maximum value described in the range
(31553789759999 99999) and set a DateTime object to that to see what actual
date and time that corresponds to. Then look at the input data and see if
you can figure out why it's resulting in a tick count
(-859032199088540 0808) that's outside the allowed range.

Somewhere you're reading a date/time value that the Mono version of
DateTime doesn't like. This may be because the Mono DateTime doesn't
handle the same range as the .NET DateTime, it might be because of some
sort of byte-swapping issue (depending on what you're running Mono on), it
might be because of some data structure packing or alignment problem, or
something else entirely. But the first step would be to figure out if the
numbers you're seeing in the exception make any sense (and at first
glance, having a negative number where only positive numbers are allowed
doesn't make sense :) ).

Pete

[Nikola Skoric]

In article <op************ ***@petes-computer.local> ,
Np*********@nno wslpianmk.com says...

What I would do is take the maximum value described in the range
(31553789759999 99999) and set a DateTime object to that to see what actual
date and time that corresponds to. Then look at the input data and see if
you can figure out why it's resulting in a tick count
(-859032199088540 0808) that's outside the allowed range.

Thanks, Pete, you have been very helpful. It turns out that
d = DateTime.FromBi nary(3155378975 999999999);
Console.WriteLi ne(d);
returns 31.12.9999 23:59:59. And
d = DateTime.Now;
Console.WriteLi ne(d.ToBinary() );
returns
-859022352112594 9343

Now, it seems like Mono and .NET Framework have some big compatibility
issues here...

--
"Now the storm has passed over me
I'm left to drift on a dead calm sea
And watch her forever through the cracks in the beams
Nailed across the doorways of the bedrooms of my dreams"

[rossum]

On Tue, 15 May 2007 20:55:11 +0200, Nikola Skoric <ni*******@net4 u.hr>
wrote:

>In article <op************ ***@petes-computer.local> ,
Np*********@nn owslpianmk.com says...

>What I would do is take the maximum value described in the range
(3155378975999 999999) and set a DateTime object to that to see what actual
date and time that corresponds to. Then look at the input data and see if
you can figure out why it's resulting in a tick count
(-859032199088540 0808) that's outside the allowed range.

Thanks, Pete, you have been very helpful. It turns out that
d = DateTime.FromBi nary(3155378975 999999999);
Console.WriteL ine(d);
returns 31.12.9999 23:59:59. And
d = DateTime.Now;
Console.WriteL ine(d.ToBinary( ));
returns
-859022352112594 9343

Now, it seems like Mono and .NET Framework have some big compatibility
issues here...

You original error messsage talked about "ticks" - the Mono
constructor seemed to need Ticks as input. What does d.Ticks return?
Is that number within the expected range?

The documentation for DateTime mentions both ToBinary() and
FromBinary() to serialize and deserialize a DateTime object. Are you
trying to serialize with ToBinary() and deserialize with a
constructor?

Try deserializing with FromBinary(), that might work better.

rossum

[Peter Duniho]

On Tue, 15 May 2007 13:49:52 -0700, rossum <ro******@coldm ail.comwrote:

[...]
The documentation for DateTime mentions both ToBinary() and
FromBinary() to serialize and deserialize a DateTime object. Are you
trying to serialize with ToBinary() and deserialize with a
constructor?

Try deserializing with FromBinary(), that might work better.

Or conversely, serializing with the Ticks property. Though, since you're
serializing to a binary data storage, I'd say the previous suggestion is
probably better (use FromBinary()). Just offering alternatives. :)

Either way, that may well be the problem.

Pete