[Mono-bugs] [Bug 502013] BlogEngine.NET: weird crashes, hangs and breakpoint errors when debugging remotely
    bugzilla_noreply at novell.com 
    bugzilla_noreply at novell.com
       
    Wed May 13 17:31:18 EDT 2009
    
    
  
http://bugzilla.novell.com/show_bug.cgi?id=502013
User mchristensen at novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=502013#c4
--- Comment #4 from Marc Christensen <mchristensen at novell.com>  2009-05-13 15:31:17 MDT ---
I often get this stack trace on the Linux server side when debugging
blogengine.net and clicking "Stop" in the windows' tray icon:
Thread @433 caught exception while sending Mono.Debugger.TargetEventArgs
(TargetExited:0:):
System.Runtime.Remoting.RemotingException: Unknown server:
tcp-pipe://2b037eea-9f59-4eee-886b-4008fb3a6318
Server stack trace: 
  at Mono.VisualStudio.Remoting.HostConnectionPool.CreateConnection ()
[0x00000] 
  at Mono.VisualStudio.Remoting.HostConnectionPool.GetConnection () [0x00000] 
  at Mono.VisualStudio.Remoting.TcpConnectionPool.GetConnection (System.String
pipeUrl) [0x00000] 
  at Mono.VisualStudio.Remoting.TcpPipeClientSink.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) [0x0006c] in
/usr/src/packages/BUILD/mono-2.4.1/mcs/class/System.Runtime.Remoting/System.Runtime.Remoting.Channels/BinaryClientFormatterSink.cs:157 
Exception rethrown at [0]: 
  at Mono.VisualStudio.Remoting.HostConnectionPool.CreateConnection ()
[0x00000] 
  at Mono.VisualStudio.Remoting.HostConnectionPool.GetConnection () [0x00000] 
  at Mono.VisualStudio.Remoting.TcpConnectionPool.GetConnection (System.String
pipeUrl) [0x00000] 
  at Mono.VisualStudio.Remoting.TcpPipeClientSink.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) [0x0006c] in
/usr/src/packages/BUILD/mono-2.4.1/mcs/class/System.Runtime.Remoting/System.Runtime.Remoting.Channels/BinaryClientFormatterSink.cs:157 
EXCEPTION: System.Runtime.Remoting.RemotingException: Unknown server:
tcp-pipe://2b037eea-9f59-4eee-886b-4008fb3a6318
Server stack trace: 
  at Mono.VisualStudio.Remoting.HostConnectionPool.CreateConnection ()
[0x00000] 
  at Mono.VisualStudio.Remoting.HostConnectionPool.GetConnection () [0x00000] 
  at Mono.VisualStudio.Remoting.TcpConnectionPool.GetConnection (System.String
pipeUrl) [0x00000] 
  at Mono.VisualStudio.Remoting.TcpPipeClientSink.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) [0x0006c] in
/usr/src/packages/BUILD/mono-2.4.1/mcs/class/System.Runtime.Remoting/System.Runtime.Remoting.Channels/BinaryClientFormatterSink.cs:157 
Exception rethrown at [0]: 
  at Mono.VisualStudio.Remoting.HostConnectionPool.CreateConnection ()
[0x00000] 
  at Mono.VisualStudio.Remoting.HostConnectionPool.GetConnection () [0x00000] 
  at Mono.VisualStudio.Remoting.TcpConnectionPool.GetConnection (System.String
pipeUrl) [0x00000] 
  at Mono.VisualStudio.Remoting.TcpPipeClientSink.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) [0x0006c] in
/usr/src/packages/BUILD/mono-2.4.1/mcs/class/System.Runtime.Remoting/System.Runtime.Remoting.Channels/BinaryClientFormatterSink.cs:157
-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
    
    
More information about the mono-bugs
mailing list