Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Ralf Habacker" To: Subject: AW: UNIX-socket problems under cygwin 1.3.2 Date: Wed, 30 May 2001 16:29:37 +0200 Message-ID: <004401c0e914$f42d6f90$6e032bb7@BRAMSCHE> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: <20010530095638.D17603@redhat.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 > -----Ursprüngliche Nachricht----- > Von: cygwin-owner AT sources DOT redhat DOT com > [mailto:cygwin-owner AT sources DOT redhat DOT com]Im Auftrag von Christopher > Faylor > Gesendet am: Mittwoch, 30. Mai 2001 15:57 > An: Cygwin > Betreff: Re: UNIX-socket problems under cygwin 1.3.2 > > On Wed, May 30, 2001 at 08:03:02AM +0200, Ralf Habacker wrote: > >> > >> RH> I have figured out another problem on cygwin 1.3.2. On ported > >> kde 1.1.2 unix > >> RH> sockets doesn't work right. The function accept() returns an > >> error. Starting > >> RH> this application under cygwin 1.1.8-2 it works. Starting the > >> app with strace > >> RH> or gdb works. > >> > >> RH> Does anyone have some hints ? > >> > >> if you'd be more specific of what error accept() returns, or tell when > >> it returns an error -- when called, or on incoming connection, or even > >> (gasp) provide a testcase, someone surely may help. > > > >I have found this > > > >socket(PF_UNIX,SOCK_STREAM,0) = 5 > >connect(5,unix_addr.sun_path=/tmp//kfm_1002_1068BRAMSCHE_0.0,size)=okay > >... > >later > >.... > >newsock = accept (sock, (struct sockaddr *) &clientname, &size)) > >Error accepting (UNIX) sock = 5 new_sock=-1 errno=113 > > > >It is curious, that if starting this app (kpanel) like below, no errors > >occurres. > > > > strace kpanel >/dev/null > > > >It seems to me, that there are some correlations between strace printing > >code and functionality of some cygwin_accept() sub functions. > Perhaps some > >statements are only executed while stracing. > > > >If you need some additional informations tell me and I will look. > > Sure, some additional information in this case would be the lines of > code in question. There is no need to speculate on the behavior of > strace when you have the ability to read the source code. Reading the code and understanding it is not the same. My main task is to port kde and I don't have very deep knowledge about the socket stuff in cygwin. I have looked in cygwin and strace, but it's heavy. :-) One question: How are you debbuging dll's ? Regards Ralf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple