[Mono-bugs] [Bug 76001][Nor] New - BinaryFormatter exceptions when called from AsyncProcessResponse()

[bugzilla-daemon at bugzilla.ximian.com]

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 martin at ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=76001

--- shadow/76001	2005-09-06 15:21:08.000000000 -0400
+++ shadow/76001.tmp.7976	2005-09-06 15:21:08.000000000 -0400
@@ -0,0 +1,34 @@
+Bug#: 76001
+Product: Mono: Runtime
+Version: 1.0
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: remoting
+AssignedTo: lluis at ximian.com                            
+ReportedBy: martin at ximian.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: BinaryFormatter exceptions when called from AsyncProcessResponse()
+
+In the debugger, I'm using three chained sinks on the server side:
+the DebuggerServerTransportSink, the BinaryServerFormatterSink and the
+DebuggerServerDispatch sink.
+
+In the dispatch sink's AsyncProcessResponse(), I'm just using
+   sink_stack.AsyncProcessResponse (msg, response_headers, stream)
+to send the result back.
+
+Everything is working fine as long as there is no SerializationException.
+
+However, if for some reason the `msg' is not serializable (for instance
+because I'm trying to return a non-serializable type), the binary formatter
+throws a SerializationException.
+
+Shouldn't it instead serialize the exception into an IMessage and pass that
+message on to the transport sink so it can be thrown in the client ?