Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <4.3.1.2.20020502105226.025d1db0@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
Date: Thu, 02 May 2002 11:00:09 -0400
To: "Rick Hellicar (QMP)" <Rick DOT Hellicar AT eml DOT ericsson DOT se>,
   "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: Compiling/running code that used to work okay!
In-Reply-To: <BBB80FB03D54D51192DA0002A56B0248CA81C2@eukbant103.uk.eu.er
 icsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 10:14 AM 5/2/2002, Rick Hellicar (QMP) wrote:
>Hi all,
>
>I'm modifying some old code I last compiled in October 2000. The code uses a 3rd-party DLL, which
>comes with an import library. It used to link without fuss against that import library and run perfectly.
>
>I've moved on to cygwin_1.3.10, gcc version 2.95.3-5, and I now get a host of "undefined references". My code
>is (currently) the same as before, and so are the DLL and its import library. Any idea why it used to compile/link
>but doesn't anymore?


Not with the given level of details, no.


>To try and fix the problem, I built my own version of the import library, using the nm, grep, dlltool route.
>This produced an import lib which did allow me to compile and link, but I get segmentation faults
>when I run the executable.
>gdb tells me:
>
>LDR: Automatic DLL Relocation in xyz.exe
>and
>LDR: D11 NIVIIO32.dll base 10000000 relocated due to collision with C:\WINNT\System32\visa32.dll
>
>Anybody understand these messages, and could they be
>associated with why the code crashes?


No, this isn't related to your code crashes.  It's just standard Windows
DLL "messiness".  If you want to get rid of the message, build your DLL 
with a different base address that doesn't conflict with others you're 
loading.  The relocation is harmless though in terms of correctness.
In terms of getting a handle on your seg faults, gdb is your best option.



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/