[Mono-bugs] [Bug 81452][Nor] New - [Maemo] Mono Runtime error using Remoting
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Wed Apr 25 12:14:42 EDT 2007
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by everaldo at simios.org.
http://bugzilla.ximian.com/show_bug.cgi?id=81452
--- shadow/81452 2007-04-25 12:14:42.000000000 -0400
+++ shadow/81452.tmp.15507 2007-04-25 12:14:42.000000000 -0400
@@ -0,0 +1,96 @@
+Bug#: 81452
+Product: Mono: Class Libraries
+Version: 1.2
+OS: GNU/Linux [Other]
+OS Details: Memo
+Status: NEW
+Resolution:
+Severity:
+Priority: Normal
+Component: System
+AssignedTo: mono-bugs at ximian.com
+ReportedBy: everaldo at simios.org
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL:
+Summary: [Maemo] Mono Runtime error using Remoting
+
+I'm trying to use a simple helloworld Runtime.Remoting application (Client
+and Server) at a N800 device (Both applications run without problem in a
+desktop ), and the following problem appears at the server when the client
+tries to connect with it:
+
+Server Stack:
+
+ Nokia-N800-10:~/MonoStuff# mono RemotingServer.exe
+ Press the enter key to exit...
+ mono[8035]: GLIB ERROR ** default - file inssel.c: line 3502
+(mono_burg_emit): should not be reached
+ aborting...
+ Stacktrace:
+
+ at
+System.Runtime.Serialization.Formatters.Binary.MessageFormatter.ReadMethodCall
+(System.IO.BinaryReader,bool,System.Runtime.Remoting.Messaging.HeaderHandler,System.Runtime.Serialization.Formatters.Binary.BinaryFormatter)
+<0xffffffff>
+ at
+System.Runtime.Serialization.Formatters.Binary.MessageFormatter.ReadMethodCall
+(System.IO.BinaryReader,bool,System.Runtime.Remoting.Messaging.HeaderHandler,System.Runtime.Serialization.Formatters.Binary.BinaryFormatter)
+<0x00218>
+
+ Native stacktrace:
+
+ mono [0x100688]
+ /usr/lib/libglib- 2.0.so.0(g_logv+0x268) [0x4115b42d]
+
+ =================================================================
+ Got a SIGABRT while executing native code. This usually indicates
+ a fatal error in the mono runtime or one of the native libraries
+ used by your application.
+ =================================================================
+
+
+and at the Client application:
+
+ Nokia-N800-10:~/MonoStuff# mono MaemoClient.exe
+
+ Unhandled Exception: System.Runtime.Remoting.RemotingException: Tcp
+transport error.
+
+ Server stack trace:
+ at
+System.Runtime.Remoting.Channels.Tcp.TcpMessageIO.ReceiveMessageStatus
+(System.IO.Stream networkStream, System.Byte[] buffer) [0x00000]
+ at
+System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage
+(IMessage msg, ITransportHeaders requestHeaders, System.IO.Stream
+requestStream, ITransportHeaders& responseHeaders, System.IO.Stream&
+responseStream) [0x00000]
+ at
+System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage
+(IMessage msg) [0x00000]
+
+ Exception rethrown at [0]:
+ ---> System.Runtime.Remoting.RemotingException : Connection closed
+ at System.Runtime.Remoting.Channels.Tcp.TcpMessageIO.StreamRead
+(System.IO.Stream networkStream, System.Byte[] buffer, Int32 count) [0x00000]
+ at
+System.Runtime.Remoting.Channels.Tcp.TcpMessageIO.ReceiveMessageStatus
+(System.IO.Stream networkStream, System.Byte[] buffer) [0x00000] --- End of
+inner exception stack trace ---
+
+ at
+System.Runtime.Remoting.Channels.Tcp.TcpMessageIO.ReceiveMessageStatus
+(System.IO.Stream networkStream, System.Byte[] buffer) [0x00000]
+ at
+System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage
+(IMessage msg, ITransportHeaders requestHeaders, System.IO.Stream
+requestStream, ITransportHeaders& responseHeaders, System.IO.Stream&
+responseStream) [0x00000]
+ at
+System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage
+(IMessage msg) [0x00000]
+
+
+The problem appears exactly when the server receives the request form the
+client.
More information about the mono-bugs
mailing list