Bug #893

avatar

Crash on connecting to a server

Added by Samuel Gyger 4141 days ago. Updated 4083 days ago.

Status:Closed Start:10/22/2013
Priority:Normal Due date:
Assigned to:avatarMirco Bauer % Done:

100%
Category:Frontend GNOME
Target version:0.10
Complexity:

 Found in Version:
Votes: 0

Description

The system is connected via SSH to a remote server. The Server version is 0.8.9.2-2
and the Client is 0.9
How to reproduce the bug:
Click Connect -> Choose a Server (with or w/o additional commands) -> Click Connect

Expected Result:
No Crash.

Stack Trace:
Exception Type:
System.Runtime.Serialization.SerializationException

Exception Message:
Unexpected binary element: 0

Exception StackTrace:
  at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, System.Exception& exc, System.Object[]& out_args) [0x00000] in <filename unknown>:0 

Exception.ToString():
System.Runtime.Serialization.SerializationException: Unexpected binary element: 0

Server stack trace: 
  at System.Runtime.Serialization.Formatters.Binary.ObjectReader.ReadObject (BinaryElement element, System.IO.BinaryReader reader, System.Int64& objectId, System.Object& value, System.Runtime.Serialization.SerializationInfo& info) [0x00000] in <filename unknown>:0 
  at System.Runtime.Serialization.Formatters.Binary.ObjectReader.ReadValue (System.IO.BinaryReader reader, System.Object parentObject, Int64 parentObjectId, System.Runtime.Serialization.SerializationInfo info, System.Type valueType, System.String fieldName, System.Reflection.MemberInfo memberInfo, System.Int32[] indices) [0x00000] in <filename unknown>:0 
  at System.Runtime.Serialization.Formatters.Binary.ObjectReader.ReadObjectContent (System.IO.BinaryReader reader, System.Runtime.Serialization.Formatters.Binary.TypeMetadata metadata, Int64 objectId, System.Object& objectInstance, System.Runtime.Serialization.SerializationInfo& info) [0x00000] in <filename unknown>:0 
  at System.Runtime.Serialization.Formatters.Binary.ObjectReader.ReadObjectInstance (System.IO.BinaryReader reader, Boolean isRuntimeObject, Boolean hasTypeInfo, System.Int64& objectId, System.Object& value, System.Runtime.Serialization.SerializationInfo& info) [0x00000] in <filename unknown>:0 
  at System.Runtime.Serialization.Formatters.Binary.ObjectReader.ReadObject (BinaryElement element, System.IO.BinaryReader reader, System.Int64& objectId, System.Object& value, System.Runtime.Serialization.SerializationInfo& info) [0x00000] in <filename unknown>:0 
  at System.Runtime.Serialization.Formatters.Binary.ObjectReader.ReadObject (BinaryElement element, System.IO.BinaryReader reader, System.Int64& objectId, System.Object& value, System.Runtime.Serialization.SerializationInfo& info) [0x00000] in <filename unknown>:0 
  at System.Runtime.Serialization.Formatters.Binary.ObjectReader.ReadNextObject (System.IO.BinaryReader reader) [0x00000] in <filename unknown>:0 
  at System.Runtime.Serialization.Formatters.Binary.ObjectReader.ReadObjectGraph (BinaryElement elem, System.IO.BinaryReader reader, Boolean readHeaders, System.Object& result, System.Runtime.Remoting.Messaging.Header[]& headers) [0x00000] in <filename unknown>:0 
  at System.Runtime.Serialization.Formatters.Binary.ObjectReader.ReadObjectGraph (System.IO.BinaryReader reader, Boolean readHeaders, System.Object& result, System.Runtime.Remoting.Messaging.Header[]& headers) [0x00000] in <filename unknown>:0 
  at System.Runtime.Serialization.Formatters.Binary.MessageFormatter.ReadMethodCall (BinaryElement elem, System.IO.BinaryReader reader, Boolean hasHeaders, System.Runtime.Remoting.Messaging.HeaderHandler headerHandler, System.Runtime.Serialization.Formatters.Binary.BinaryFormatter formatter) [0x00000] in <filename unknown>:0 
  at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.NoCheckDeserialize (System.IO.Stream serializationStream, System.Runtime.Remoting.Messaging.HeaderHandler handler) [0x00000] in <filename unknown>:0 
  at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize (System.IO.Stream serializationStream, System.Runtime.Remoting.Messaging.HeaderHandler handler) [0x00000] in <filename unknown>:0 
  at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage (IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, System.IO.Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, System.IO.Stream& responseStream) [0x00000] in <filename unknown>:0 

Exception rethrown at [0]: 

  at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, System.Exception& exc, System.Object[]& out_args) [0x00000] in <filename unknown>:0

Associated revisions

Revision cabaeae8453a18803b989b24d88527ea2f315306
Added by Mirco Bauer 4089 days ago

Engine, Frontend-GNOME: restored ABI compat with smuxi-servers < 0.8.11 (closes: #893)

History

Updated by Mirco Bauer 4141 days ago

avatar

This issue could be a .NET 2.0 vs 4.0 issue, unfortunately the stack trace is not very helpful. Please run this command and paste the result:

monodis --assemblyref /usr/lib/smuxi/smuxi-server.exe

Updated by Samuel Gyger 4141 days ago

avatar
produces the following output.
$> monodis --assemblyref /usr/lib/smuxi/smuxi-server.exe
AssemblyRef Table
1: Version=4.0.0.0
    Name=mscorlib
    Flags=0x00000000
    Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 
2: Version=1.2.10.0
    Name=log4net
    Flags=0x00000000
    Public Key:
0x00000000: A5 71 5C C6 D5 C3 54 0B 
3: Version=0.8.9.2
    Name=smuxi-common
    Flags=0x00000000
    Zero sized public key
4: Version=0.8.9.2
    Name=smuxi-engine
    Flags=0x00000000
    Zero sized public key
5: Version=4.0.0.0
    Name=System.Runtime.Remoting
    Flags=0x00000000
    Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 
6: Version=4.0.0.0
    Name=System
    Flags=0x00000000
    Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89

Updated by Mirco Bauer 4141 days ago

avatar

That looks ok, please do the same with the frontend:

monodis --assemblyref /usr/lib/smuxi/smuxi-frontend-gnome.exe

Updated by Samuel Gyger 4141 days ago

avatar
Here you go.
 monodis --assemblyref smuxi-frontend-gnome.exe
AssemblyRef Table
1: Version=2.12.0.0
    Name=gtk-sharp
    Flags=0x00000000
    Public Key:
0x00000000: 35 E1 01 95 DA B3 C9 9F 
2: Version=4.0.0.0
    Name=mscorlib
    Flags=0x00000000
    Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 
3: Version=0.9.0.0
    Name=smuxi-common
    Flags=0x00000000
    Zero sized public key
4: Version=2.12.0.0
    Name=gdk-sharp
    Flags=0x00000000
    Public Key:
0x00000000: 35 E1 01 95 DA B3 C9 9F 
5: Version=4.0.0.0
    Name=Mono.Posix
    Flags=0x00000000
    Public Key:
0x00000000: 07 38 EB 9F 13 2E D7 56 
6: Version=2.12.0.0
    Name=glib-sharp
    Flags=0x00000000
    Public Key:
0x00000000: 35 E1 01 95 DA B3 C9 9F 
7: Version=1.2.10.0
    Name=log4net
    Flags=0x00000000
    Public Key:
0x00000000: 04 6E D8 BA 4E AE 38 AD 
8: Version=4.0.0.0
    Name=System
    Flags=0x00000000
    Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 
9: Version=0.9.0.0
    Name=smuxi-engine
    Flags=0x00000000
    Zero sized public key
10: Version=0.9.0.0
    Name=smuxi-frontend
    Flags=0x00000000
    Zero sized public key
11: Version=2.12.0.0
    Name=pango-sharp
    Flags=0x00000000
    Public Key:
0x00000000: 35 E1 01 95 DA B3 C9 9F 
12: Version=4.0.0.0
    Name=System.Core
    Flags=0x00000000
    Public Key:
0x00000000: B7 7A 5C 56 19 34 E0 89 
13: Version=1.0.0.0
    Name=dbus-sharp-glib
    Flags=0x00000000
    Public Key:
0x00000000: 56 75 B0 C3 09 31 15 B5 
14: Version=1.0.0.0
    Name=dbus-sharp
    Flags=0x00000000
    Public Key:
0x00000000: 56 75 B0 C3 09 31 15 B5 
15: Version=2.12.0.0
    Name=glade-sharp
    Flags=0x00000000
    Public Key:
0x00000000: 35 E1 01 95 DA B3 C9 9F

Updated by Mirco Bauer 4137 days ago

avatar
  • Target version changed from 0.9 to 26

Updated by Mirco Bauer 4107 days ago

avatar

There is no known fix for this yet. The issue can be avoided though by upgrading the smuxi-server to a newer version.

Updated by Mirco Bauer 4106 days ago

avatar

Looks like the problem is that 0.8.9.2 uses an automatic serializer for the ServerModel type which receives a _ServerID field from a newer Smuxi frontend (like 0.9) but doesn't know what to do with it.

Updated by Mirco Bauer 4083 days ago

avatar
  • Status changed from New to Closed
  • % Done changed from 0 to 100

Updated by Mirco Bauer 4083 days ago

avatar
  • Target version changed from 26 to 0.10

Also available in: Atom PDF