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
From: "Ralf Habacker" <Ralf DOT Habacker AT saght DOT tessag DOT com>
To: "Cygwin Users" <cygwin AT cygwin DOT com>
Subject: AW: AW: UNIX-socket problems under cygwin 1.3.2 -addon
Date: Wed, 30 May 2001 17:01:46 +0200
Message-ID: <004901c0e919$721a3bf0$6e032bb7@BRAMSCHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
In-Reply-To: <3B150722.686681F0@yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

> Von: cygwin-owner AT sources DOT redhat DOT com
> [mailto:cygwin-owner AT sources DOT redhat DOT com]Im Auftrag von Earnie Boyd
> Gesendet am: Mittwoch, 30. Mai 2001 16:44
> An: Ralf Habacker
> Cc: cygwin AT cygwin DOT com
> Betreff: Re: AW: UNIX-socket problems under cygwin 1.3.2 -addon
>
> 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.
>
Okay, that might be, but when I use cygwin 1.1.8 with the same code there
isn't any error.
I have checked this with a little application with a little dll printing
something and have the same result.

So my next question is, if there are some changes in dll initialisation. I'm
using this below

By the way: I like cygwin and think that all people working on it have done
a great work.

Ralf

----------------------------------------------------------------------------
-
#define WIN32_LEAN_AND_MEAN
#include <windows.h>
#undef WIN32_LEAN_AND_MEAN
#include <stdio.h>

#ifdef __cplusplus
extern "C" {
#endif
BOOL APIENTRY DllMain (HINSTANCE hInst, DWORD reason, LPVOID reserved);

#include <cygwin/cygwin_dll.h>
DECLARE_CYGWIN_DLL( DllMain );
HINSTANCE __hDllInstance_base;
#ifdef __cplusplus
}
#endif
BOOL APIENTRY
DllMain (HINSTANCE hInst, DWORD reason, LPVOID reserved)
{
  __hDllInstance_base = hInst;
  return TRUE;
}
----------------------------------------------------------------------------


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