Ok - I have created a new issue -- https://github.com/mobile-shell/mosh/issues/705 -- with the information you asked for. When I was typing, I think I was just typing garbage, but I have also tried systematically typing the alphabet and it doesn't seem like a particular character is the culprit.
Thanks, Dan On Sat, Dec 26, 2015 at 3:34 PM john hood <cg...@glup.org> wrote: > Oh, Cygwin, that beloved reliable Unix emulation. > > There is a problem in the trace, I see mosh-client reading both the > network socket and terminal input after select() returns 0 fds ready...and > this is mysterious. > > I think the behavior with script may be about the type of terminal Mosh is > running on in Cygwin, rather than character encoding. IIRC Cygwin handles > ptys and "real" terminals differently (and I think a Cygwin command invoked > in a Windows console is a third variant) > > We need more info. Please open an issue at > https://github.com/mobile-shell/mosh/issues/new with this info: > > OSes and versions on both client and server > mosh version on both client and server > Where did you get the client mosh from? The Cygwin installer or a local > build? > What are you using for the Cygwin terminal? Are you invoking Mosh from a > Unix or Windows shell prompt? > What, if any, is the message mosh-client prints on exit? (A screenshot of > the terminal window would be nice, if possible.) > In the trace you've given, you appear to be typing at Mosh when the > session closes. What were you typing? > > regards, > > --jh > > > On 12/26/15 1:59 PM, Dan Schwartz wrote: > > Thanks John - > I tried these with the following outcomes: > > * --no-init did not provide any additional information > * Interestingly, when I run mosh under script, I do not reproduce the > problem. The mosh-client does not exit. I can use this as a workaround for > now I guess. Maybe this points in the direction of a character encoding > issue? > * I have attached the strace output from my system. I'm running this in > cygwin on a machine that is running Windows 10.1. I can't say that I'm > immediately able to glean anything from this output. > > Thanks, > Dan > > On Fri, Dec 25, 2015 at 10:45 PM john hood < <cg...@glup.org> > cg...@glup.org> wrote: > >> On 12/24/15 8:06 AM, Dan Schwartz wrote: >> > Hi mosh community - >> > >> > I'm trying to get set up with mosh, and I'm having an issue that the >> > mosh-client is exiting unexpectedly (at least I think it is the >> > mosh-client that causes this). I am able to establish a connection >> > between the client and server - the server is receiving packets, and I >> > can even run 'ls' and get back directory contents if I am fast >> > enough...and then the client exits (regardless of what I type, the >> > client seems to exit after between 30s and 1 minute). The server side >> > debug info is pasted below. I see a 'received state -1' which seems >> > suspicious, but I'm not sure what this means or how to debug what's >> > happening. >> > >> > Any help would be appreciated. >> > >> > Thanks, >> > Dan >> > >> > Here is the server side debug info: >> > >> > [24498] Sent [26=>29] id 29, frag 0 ack=24, throwaway=26, len=54, >> > frame rate=31.25, timeout=102, srtt=62.7 >> > [24532] Sent [26=>30] id 30, frag 0 ack=24, throwaway=26, len=48, >> > frame rate=31.25, timeout=102, srtt=62.7 >> > [24565] Received state -1 [coming from 24, ack 29] >> > [24565] Sent [29=>30] id 31, frag 0 ack=-1, throwaway=29, len=43, >> > frame rate=31.25, timeout=97, srtt=63.3 >> > >> > [mosh-server is exiting.] >> Yes, state -1 is a request for shutdown. So your client is terminating >> in a somewhat-orderly way. The question is, why is it doing this >> without any action from you or the server? >> >> Things to try: >> >> * Start mosh with the --no-init option. Sometimes errors are written >> just before the screen is cleared on exit. This option disables that >> screen clearing. >> * If that fails, use the script command to get a typescript of your >> session. >> * If neither of these produce anything useful, please try using your OS >> system-call tracer (truss, ktrace, dtrace) to capture a record of what >> mosh-client is actually doing. >> >> Please open an issue on Github with anything you find, it's the best way >> to handle problems like this. >> >> regards, >> >> --jh >> > >
_______________________________________________ mosh-users mailing list mosh-users@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh-users