[Mono-dev] Socket.Accept() causes + Stopped
djleehaha at googlemail.com
Thu Sep 29 03:09:58 EDT 2011
ahh, that kinda makes sense - although I am not expecting my bash script to
require user input.
Thanks for the pointer, I'll do some more digging
btw - what's the convention in here? top or bottom post? does it matter?
On 28 September 2011 20:03, Robert Jordan [via Mono] <
ml-node+s1490590n3852537h88 at n4.nabble.com> wrote:
> On 27.09.2011 15:28, DJL wrote:
> > 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.
> > Short version:
> > Calling Socket.Accept() is causing my application to freeze. A
> > "fg" resumes it.
> It's not your application that freezes. You seem to be invoking
> bash and some tool that sends SIGTSTP to itself. SIGTSTP is used
> when an application/command requires a terminal for user input,
> e.g. password input.
> > Long version:
> > 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
> > 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:
> > /
> > Log(9, "pcsBash.Start()");
> > pcsBash.Start();
> > Log(9, "<");
> > stStdIn = pcsBash.StandardInput.BaseStream;
> > stStdErr = pcsBash.StandardOutput.BaseStream;
> > Log(9, "Accept()");
> > sktStdOut = sktStdOutListen.Accept();
> > Log(9, "<");
> > stStdOut = new System.Net.Sockets.NetworkStream(sktStdOut, true);
> > Log(9, "<");/
> > Looking in the log when it stops (before typing fg) the last entry is
> > "Accept()"
> > (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
> > 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
> > do anything out of the ordinary - although I imagine if it did the
> > might be quite different?
> > Once again, thanks for any help you can give on this baffling issue
> > System info:
> > /#mono --version
> > Mono JIT compiler version 2.8.2 (tarball Wed Feb 23 09:31:21 UTC 2011)
> > Copyright (C) 2002-2010 Novell, Inc and Contributors.
> > TLS: __thread
> > SIGSEGV: altstack
> > Notifications: epoll
> > Architecture: amd64
> > Disabled: none
> > Misc: debugger softdebug
> > LLVM: supported, not enabled.
> > GC: Included Boehm (with typed GC and Parallel Mark)
> > #uname -a
> > Linux svn 188.8.131.52-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:
> > Sent from the Mono - Dev mailing list archive at Nabble.com.
> Mono-devel-list mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=3852537&i=0>
> If you reply to this email, your message will be added to the discussion
> To unsubscribe from Socket.Accept() causes + Stopped, click here<http://mono.1490590.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3847351&code=ZGpsZWVoYWhhQGdvb2dsZW1haWwuY29tfDM4NDczNTF8LTE4NjEwNDU2Nzk=>.
*DJL - XWAX And Vinyl DJ http://www.dj-djl.com
Wednesday 8-10PM CH1 http://www.housefreaks.co.uk
DJL's Deep Decks live every Wednesday night from 8PM* on www.housefreaks.co.uk Channel1 - Deep/Tech & Minimal House
View this message in context: http://mono.1490590.n4.nabble.com/Socket-Accept-causes-1-Stopped-tp3847351p3854598.html
Sent from the Mono - Dev mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list