Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Wed, 30 May 2001 10:31:54 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: UNIX-socket problems under cygwin 1.3.2
Message-ID:	<20010530103154.A18223@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20010530095638 DOT D17603 AT redhat DOT com> <004401c0e914$f42d6f90$6e032bb7 AT BRAMSCHE>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<004401c0e914$f42d6f90$6e032bb7@BRAMSCHE>; from Ralf.Habacker@saght.tessag.com on Wed, May 30, 2001 at 04:29:37PM +0200

On Wed, May 30, 2001 at 04:29:37PM +0200, Ralf Habacker wrote:
>cgf says:
>> 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. :-)

I must disagree.  Strace output is handled with things like "debug_printf"
or "syscall_printf" or "strace_printf".  It's really pretty trivial.

>One question: How are you debbuging dll's ?

With gdb.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -