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 X-Apparently-From: Message-ID: <3B150722.686681F0@yahoo.com> Date: Wed, 30 May 2001 10:43:46 -0400 From: Earnie Boyd Reply-To: Cygwin Users X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Ralf Habacker CC: cygwin AT cygwin DOT com Subject: Re: AW: UNIX-socket problems under cygwin 1.3.2 -addon References: <004501c0e915$a4826d50$6e032bb7 AT BRAMSCHE> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ralf Habacker wrote: > > > > > 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. :-) > Heavy only when you don't want to handle the task. Yes it may take time to understand but wanting to take that time is different from the understanding. > One question: How are you debbuging dll's ? Chris already answered that question, use gdb. > Second Question: How do you debug an error in cygwin1.dll which will only be > existant, when !strace && !debbuging ? > You assume the error to be Cygwin's in this case?!? I would first look for uninitialized pointers to memory in your own code. This is the usual cause for this type of condition. -- Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple