[Mono-dev] Socket.Accept() causes + Stopped
djleehaha at googlemail.com
Tue Sep 27 09:28:50 EDT 2011
Hi everyone, first post on here.
I'm getting a bizzarre behaviour and I'm hoping you guys can help.
Sorry if this is the wrong place to post this.
Calling Socket.Accept() is causing my application to freeze. A commandline
"fg" resumes it.
Ok so I have a multi-threaded, Multi DLL application.
Several of these DLLs are calling Socket.Accept() without issue.
However the newest of these is causing the application to stop every time.
The commandline shows "+ Stopped" and no other output.
typing "fg" causes the application to continue as if nothing happened.
Here is an excerpt from my code:
stStdIn = pcsBash.StandardInput.BaseStream;
stStdErr = pcsBash.StandardOutput.BaseStream;
sktStdOut = sktStdOutListen.Accept();
stStdOut = new System.Net.Sockets.NetworkStream(sktStdOut, true);
Looking in the log when it stops (before typing fg) the last entry is
(And yes the log is being flushed after each line).
It is always in this same place, which leads me to suspect it is NOT one of
the other threads causing this.
Anyone have any ideas what could possibly cause this?
Incidentally - the same code running on Windows in Microsoft's .Net does not
do anything out of the ordinary - although I imagine if it did the symptoms
might be quite different?
Once again, thanks for any help you can give on this baffling issue
Mono JIT compiler version 2.8.2 (tarball Wed Feb 23 09:31:21 UTC 2011)
Copyright (C) 2002-2010 Novell, Inc and Contributors. www.mono-project.com
Misc: debugger softdebug
LLVM: supported, not enabled.
GC: Included Boehm (with typed GC and Parallel Mark)
Linux svn 220.127.116.11-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200
x86_64 x86_64 x86_64 GNU/Linux
View this message in context: http://mono.1490590.n4.nabble.com/Socket-Accept-causes-1-Stopped-tp3847351p3847351.html
Sent from the Mono - Dev mailing list archive at Nabble.com.
More information about the Mono-devel-list