Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <3.0.1.32.19990428101831.0068af90@pop.iperbole.bologna.it>
X-Sender: vaf9143 AT pop DOT iperbole DOT bologna DOT it
X-Mailer: Windows Eudora Light Version 3.0.1 (32)
Date: Wed, 28 Apr 1999 10:18:31 +0200
To: cygwin AT sourceware DOT cygnus DOT com
From: Glauco Masotti <vaf9143 AT madrona-a DOT iperbole DOT bologna DOT it>
Subject: s.v. at XOpenDisplay... help please!
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hello. Nobody answered to my previuos posting. 
The problem I hit seems to me really a bug in the distibution,
and I am really stuck here, thinking of converting all my code
using OpenGL and MSVC (at least it works... and you can debug). 
Here is my previous posting:
========================================================================
Hi there.
From one side I am glad to tell you that I finally succeded in building 
any kind of dll and getting them loaded by ME10 (ref.: mixing GNU and MS 
tools/libraries...). *Some* of them also work fine :-)
Maybe in another mail I tell you my point of view about this experience.

I also succeded in getting an authonomuos program working fine using the
Cygwin dll
(not with Mingw, but this is another story).
This program makes substantial graphics I/O and I could port it from an X ws
to a Win NT pc, without substantial changes to the sources.

From the other side I must say that I hit a rock which may sink this
project if
a solution is not found quickly.
The problem now is to be able to open an X terminal from a dll that I have
loaded
in ME10. This is not working here (I am using a plain Cygwin 20.1
distribution).
The graphics interface of this dll shares most of the code of the other
program,
so I cannot figure out why the program runs and the dll doesn't.
I even wrote a very simple dll which just makes a call to XOpenDisplay.
Well, no way, I get a segmentation violation signal.
Is this a known problem? Can someone help? 

BTW, debugging a dll loaded at run time is very hard given the available
tools. 
The main problem is that I cannot set a breakpoint in the dll code before
actually
loading it, but after I have loaded it, gdb is unresponsive to ^C like it
does on a ws.
Can someone tell me the magic to get gdb sense the interrupts?

Regards,
--- Glauco Masotti





--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com